Re: java serialization alternative

That's a rather prejudicial statement.

We use embedded Derby+Hibernate and I have not found it to be either
cumbersome or fragile. Hibernate took a bit of getting used to but once
I found a recipe that worked, varying it wasn't all that bad.

Donald

Jeff Kesselman wrote:
> OTOH Object mappings to RDBMSs are cumbersome, fragile and create a code
> dependency that is orthogonal to your regular code base.
>
> There ain't no one magic bullet.
>
> JK
>
>
> Olivier Lefevre wrote:
>> --- Bob Lee <[email protected]> wrote:
>>
>>> Serialization sounds good in theory, but you really want to decouple
>>> your code from its persistent state. [...] I think this is one of many
>>> reasons why relational databases are still so much more popular for
>>> long term persistence.
>>>
>>
>> And, a contrario, that is probably one reason why pure OO databases
>> flopped: to deliver the expected benefits they must store objects
>> pretty much as they exist in the application but then you get the
>> same evolution headaches as with serialization. Is that correct? I
>> wasn't really around back then (just starting).

===================================
This list is hosted by DevelopMentor®  http://www.develop.com

View archives and manage your subscription(s) at http://discuss.develop.com