But after looking closely at the list of a possible properties, i found out that some of them depend on others. For example, if item is a PDF document, it can have an index. But a document can also have an index with links. Logically, a properties like 'index with links' don't belong to the verification table - they look like a kind of a composite field - 'index with links' is not a stand-alone property, but it also implies that an item also has an 'index' property. On the other hand, it is impossible to decouple 'index' from 'with links', because the second part won't have any meaning without the first part.
You mean your properties would be better organized as a tree ? Or is it even more complicated than that ?
If it's a tree, look at the ways of storing a tree in a table.
---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives?
http://archives.postgresql.org
