Carl Rosenberger wrote:
>Scott Reed wrote:
>> I tried TP/A with our fairly large application,
>> enhancing only the classes that are persisted,
>
>Makes sense but please note:
>If you change members of objects that are persisted
>elsewhere in your code, db4o has no way of knowing
>about the changes.
All non-final data members are private and only modifiable from elsewhere in the code only via method calls.
>> ran into a lot of problems and gave up,
>
>It would be cool if you could tell us about the
>problems, so we can improve.
>
>Whenever you run across a problem, please tell
>us first.
I mentioned this in an earlier post (VerifyError with Db4oInstrumentationLauncher). Patrick asked me to
send in the code but it was difficult to isolate. It's a large code
base and mostly proprietary. We need to know more about your policies
and procedures in handling customer code before we could send anything
in.
>Whenever you think db4o is nice, please tell
>the world out there.
Definitely. I'm believer! I've been using db4o since the mid-90's.
>> What do you mean by "assemblies"?
>
>Probably .NET assemblies.
>
>Maybe you are a Java user? The equivalent would
>be "Java .jars".
Yes, I've had no experience with .net at all except the unhappy experience of trying to install multiple versions for a couple of VB projects.