Ashok is now away for a few weeks, so he will not be able to have a look. Versioning was not included when the new schema was done. We are not using it and did not look into the details of it.
In what ways does the versioning break it? maybe we can then work out how to extend the schema for that. rgds CB > >> Modifying J2EEStore to do what said above does not help : I got an > >> ObjectNotFoundException (/users) on slide's initialization. > >> If JEEStore with old schema is not breaking RevisionDescriptorsStore > >> I will have to swith back to it for now :-( > > > > > > I have tons of problems with referential integrity violations. For the > > beginning, I removed all those constraints and tried to make the store > > pass the functional tests without serious failures. However, even in > > that I did not succeed yet. Any help would be much appreciated. > > I think that these constraints are not the real problem but that it is > the new schema > that doesn't take into account versionning related stuff. > So removing these contraints will not help in making this store pass the > tests, > but new schema and store methods have to be modified. > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
