durusmail: durus-users: Re: A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
Trivial doc/interface fix
2006-03-13
Re: Trivial doc/interface fix
2006-03-13
2006-03-13
A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
2006-03-13
Re: A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
2006-03-13
Re: A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
2006-03-14
Re: A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
2006-03-14
Re: A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
2006-03-14
Re: A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
2006-03-14
2006-03-13
2006-03-21
Re: A new backend storage (Re: [Durus-users] Re: Trivial doc/interface fix)
David Binger
2006-03-14
On Mar 13, 2006, at 8:32 PM, Peter Fein wrote:

> Peter Wilkinson wrote:
>>
>> On 14/03/2006, at 9:18 AM, Jesus Cea wrote:
>>
>>> I have several small issues, nevertheless. For example, objects
>>> come to
>>> the storage engine already serialized. I would rather prefer to
>>> do the
>>> serialization myself. I don't need, for example, to keep the
>>> first eight
>>> bytes of the object in the database, since that is the OID and I
>>> already
>>> have the OID as the database key.
>>
>> I'll second this, my previous email makes note of the same thing,
>> different reasons but basically the same need.
>
> Third, if I understand correctly.

This is an interesting idea.  We'll see what we can do
to make it happen.


reply