-
I am surprised to discover that NeoDatis doesn't seem to offer ACID transactions. I run the attached testcase and pull the power cable after the program has been running for a few seconds. When I restart, I discover that the database file is corrupt (running the testcase causes an exception to be thrown).
Please let me know if you can reproduce this.
2009-11-19 22:50:43 UTC in NeoDatis ODB
-
No, there was no exception prior to this one.
2009-11-19 16:17:13 UTC in NeoDatis ODB
-
Olivier,
Try this instead:
Objects getObjects(Class clazz);
I believe the compiler will be smart enough to figure out type T using the argument. When you use a raw type Class the compiler will default T=Object unless you have a Generic return type. This breaks in the following case:
someMethod(odb.getObjects(Data.class));
The Java6 compiler will not be smart enough to link the...
2009-11-19 16:16:33 UTC in NeoDatis ODB
-
akahanek,
From personal experience, the more configuration options you add, the harder it is for end-users to use the software and for the developers to maintain it.
As mentioned before, I am in favor of adding configuration options *on demand*. If users bring up real-life use-cases (not theoretical "I think I'd need this one day") and there is sufficient demand for this feature (a large...
2009-11-18 23:21:28 UTC in NeoDatis ODB
-
Unfortunately it went away for me after a reboot. As I said, it looks like a race condition. I guess we can close this issue for now.
2009-11-18 23:16:28 UTC in NeoDatis ODB
-
Hi,
Instead of:
Objects getObjects(Class clazz);
you should use:
Objects getObjects(Class clazz);
Right now the compiler cannot figure out that the return type depends on your argument because you are passing in a raw type Class.
2009-11-18 21:17:59 UTC in NeoDatis ODB
-
Hi,
I got the following NPE randomly. I haven't been able to reproduce it since but the stack-trace might give you an idea as to what was wrong. Version = 1.9.20-665
Exception in thread "main" java.lang.NullPointerException
at org.neodatis.odb.impl.core.layers.layer3.buffer.MultiBufferedFileIO.goToPosition(MultiBufferedFileIO.java:101)
at...
2009-11-18 21:08:16 UTC in NeoDatis ODB
-
Olivier,
For my part, I think a global query setting is only useful if you auto-populate fields outside the query depth. If you have to populate dependencies manually then you might as well set the depth manually on each of your queries (different classes will need different depths).
I want as few configuration options as possible. I expect NeoDatis to do the right thing most of the time...
2009-11-18 19:44:15 UTC in NeoDatis ODB
-
Version 1.9.20-665.
2009-11-18 19:34:18 UTC in NeoDatis ODB
-
Version 1.9.20-665.
2009-11-18 19:33:50 UTC in NeoDatis ODB
