james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eric Charles <e...@u-mangate.com>
Subject Re: JPA for imap 0.1 release
Date Fri, 25 Jun 2010 03:16:09 GMT
Hi Tim,

If we set streaming by default, we can not use derby anymore as default.

With a different provider, schema may be different.
Do you mean we should ensure with specific annotations that schema will 
always be the same?

Tks,

Eric


On 06/24/2010 10:31 PM, Tim-Christian Mundt wrote:
> Hi,
>
>    
>> 4. The majority of the classes will use openjpa classes: instead of
>> moving them all to org.apache.james.imap.jpa.mail.model.openjpa package,
>> we leave them and we rename this package to
>> org.apache.james.imap.jpa.mail.model.streaming to reflect that it goes
>> on "streaming the blobs".
>>      
> With OpenJPA you can still choose whether to use streaming, right?
> Because some databases don't support it. I think we should make
> streaming the default.
>
>    
>> The definition of an alternate JPA provider should not clash with the
>> proprietary extensions (still need to test it).
>>      
> However, the usage of another JPA provider would result in a different
> database scheme, doesn't it? We could add implementations for a the
> other two providers you mentioned.
>
> Best
> Tim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>    


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message