Re: How will schemas be affected by nested relations?

> If some future project determines that one of the "things" previously identified as a property in our database schema should now be seen as an entity, then migrate/change the database solution (refactor).

This is not the case with dbd. And it isn't by accident or luck. I took nearly half a decade to find a method of representing things so that any "entity", "attribute", "value", etc can itself have attributes and values and so on forever without requiring one to revise the schema and migrate data. I can demonstrate this by showing that the initial script/queries/data are less affected when meeting future unknown data requirements compared to any other methodology. Would someone be willing to engage in a simple example of their choosing? Received on Mon Jul 24 2006 - 21:16:54 CEST