> Thus, they are removed because the import / dump of postgresql didnt > work. > There was no shortcoming in MMBase why it has been removed? > (or are you refering to the MMBase-Applicaion-Import) > When i would implement an Oracle resource, that does foreignkey-checks. > Do you see any problems? first problem: The problem with the postgress check_number hack is that it's not a constraint but some kind of stored procedure. Now when you import data durring the import the database will not be consitent and the import fails since it's not possible to disable "stored procedures" when importing.
second problem: the check_number hack is nice but it only implements half of the required functionality. If you import data via apps1 syncnodes are created (nodes with NODE type fields) but if afther that you remove the imported node the syncnode is not removed. this not only keeps your data inconstistent but really makes it impossible to import the data later on. third problem: One other problem is that the "function" is not dropped if you drop the database > > > Btw I still have to create proper documentation on setting up the > > resource, so I don't blame people for not realizing what is possible > > with the new layer. > If i have feedback, i will send it you > > -- Kees Jongenburger Mediapark C101 Hilversum +31 (0)35 6772910
