Nico, Thanks for your input!
On Wednesday 15 March 2006 13:28, Nico Klasens wrote: > let me guess. You have upgraded or started using mysql 4.1. This version > returns an optimized resultset which filters out duplicate nodes. We're currently using MySQL 4.0.18. The test/staging and production databases are currently running on the same MySQL server. The only difference between the test/staging and production environment is the Didactor version. A developer did mention however that they did something with the storage layer and since this particular database has been running (and migrated) for quite some time now it could be we're currently looking at plain old database inconsistency. Could you please explain, from a developer perspective, what piece of the code is triggering this error so I can have one of our developers look into this? The one question remaining is: how serious is this error? What happens when this piece of software is put in production without fixing what's causing this error? > Or you are missing the typerel for allowed relation > learnblocks->pos2rel->images or the application does a call for > relatednodes which is not possible in the current model. > First case is configuration. Second case is code This could be the missing typerel. I'll have a look at this. Thanks again! Arjen
pgpCxOTZHBJuC.pgp
Description: PGP signature
_______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
