Tag Info

New answers tagged

2

Bill Karwin covers the alternatives well in his presentation. I have a few notes on a similar but slightly different closure table in: http://dustbite.se/tree/ The idea is to have one table that represents the parent relation, and another that represents the ancestor relation. All changes to the ancestor relation is a consequence of a change in the ...


2

I would create a separate table for history. If it was me, I would use an auto-increment column for the primary key (historyID) , a column for the vial ID, and a column for a location ID. I would think the vial ID would be foreign key to the nodes table. You could then query against a vial to see it's full history. Since you don't list what your lookup ...



Top 50 recent answers are included