> Well, if this is the only point on were it misbehaviours, im prepared to > create an Postgres73.java. actualy for the moment i am for removing the function from the classes because they only perform haft of the work (creating even more problems)
it's usefull because you cannot add illega node type fields but it does not preserve the consitency over time. one problem i had was that I imported data using mmapps1.0 (with syncnode) and after a while wee needed to move the database to another database but the import failed because the syncnodes where pointing to non existant nodes. (this is all because the function is working during an import). the same problem occurs if you database dump first tries to import the insrel table. > -but- then the lookup.xml should point to the proper classes, and not > the storage classes (all lookup_postgresql.xml info points to > postgresql.xml --> org.mmbase.storage.database.PostgreSqlStorage > Why has this been changed and by whom? (also: lookup_postgresql.xml is > not an valid xml!) well it is used as an entity in the lookup.xml so i don't see the problem
