Hi Andy, hi Matthew,
I agree with Matthew that in order to support read only datastores we
have to deal with modifications of PCs. I am wondering which operation
would result in an exception. How about commit or flush throwing an
exception if any modification is about to be flushed to the datastore?
JDOReadOnlyException sounds good to me.
Regards Michael
Why not also require modifications to PCs to throw JDOUserException?
Further, the exception could be a new extension of JDOUserException
called JDOReadOnlyException.
Andy Jefferson wrote:
Something that we've been asked for several times is where a user has
a datastore that is outside their control and they either don't have
permission to write to it, or maybe they have permissions but don't
want to write to it.
Propose :-
PMF property (with setter/getter)
javax.jdo.option.ReadOnly - values true | false
Behaviour :-
Use of makePersistentXXX(), deletePersistentXXX() will throw
JDOUserException.
Use of query.deletePersistentAll() will throw JDOUserException
--
*Michael Bouschen*
*Prokurist*
akquinet [EMAIL PROTECTED] GmbH
Tempelhofer Ufer 23-24, D-10963 Berlin
Bülowstr. 66, D-10783 Berlin
Fon: +49 30 235 520-33
Fax: +49 30 217 520-12
Email: [EMAIL PROTECTED]
Url: www.akquinet.de <http://www.akquinet.de>
akquinet [EMAIL PROTECTED] GmbH, Berlin
Geschäftsführung: Prof. Dr. Christian Roth, Hendrik Saly, Martin Weber
Amtsgericht Berlin-Charlottenburg HRB 86780
USt.-Id. Nr.: DE 225 964 680
