On Thursday, May 19, 2016 04:22:44 PM Bert Massop wrote: > To xor: a4378e0 seems to be at the root of this problem. Is it at all > possible to unit test this upgrade path?
If by "upgrade path" you mean "running a WoT with a new database format version on an old database": There is no infrastructure for that yet because that would be rather complex. This is because database schema changes in db4o are "implicit": Db4o will automatically adapt the class layout it has stored to certain types of changes (but not to all types IIRC) of the Java class structure. So to test this, we would need both a JAR with the old classes and a JAR with the new classes, and somehow load them one after the other - which is rather complex from a Git / Ant point of view I suppose. But: The stack trace we're talking about here is usually always executed (as long as a db4o file is pre-existing), not only if the database format version changes. So it may be possible to add unit tests for this particular issue - but as you can see from my other mail, your suspected cause of the issue doesn't seem to be the case, so I don't even know yet what we would want to test... :|
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
