I don't see JPA JDO integration in either of these lists (except regarding
PersistenceManagerFactory configuration and Java 5.0 annotations).
Ilan
- Original Message -
From: Craig L Russell
To: JDO Expert Group ; Apache JDO project
Sent: Monday, October 16, 2006 1:39 AM
Subje
Javadogs,Please refer to http://wiki.apache.org/jdo/ChangeLog and http://wiki.apache.org/jdo/ChangeLog15I've updated the wiki pages with everything that I know that we plan to do for the maintenance release.Please carefully review these wiki pages and let me know if I've missed anything. Please rep
Javadogs,For easier development of web applications, it would be nice if PersistenceManager were Serializable. There is nothing stopping an implementation from declaring that their implementation extends Serializable, but the behavior is implementation-specific.For the maintenance release, I'd like
I'd like to consider adding a way for a query in metadata to specify the fetch plan to be used with that query. And possibly a way for the application to define on an application basis which fetch plan to be used. Perhaps a class and method name binding to a fetch plan, so any query or retrieval ma
Hi Andy,
My comments only apply to requiring standard support for Calendar. Of
course, individual implementations are free to support Calendar as a
field type and impose whatever restrictions they want on its use.
If enough implementations do this, I'm open to formalizing the
support in f
indexed and unique are certainly being used - also in Element, Key
and Value. I do not use deleteAction, sequence and valueStrategy
yet, but I think that it might make sense to use them in the future.
OK.
The point that this raises is that my understanding of the "split" JDO-ORM
was
to separate
> indexed and unique are certainly being used - also in Element, Key
> and Value. I do not use deleteAction, sequence and valueStrategy
> yet, but I think that it might make sense to use them in the future.
OK.
The point that this raises is that my understanding of the "split" JDO-ORM was
to sepa
Hi Ilan,
I agree that mappedBy should remain in Field. Same is true for indexed,
unique, deleteAction, sequence and valueStrategy, which can all be
useful also for object databases. I think that only table, column and
columns are specific for relational databases. Same is applied also for
Eleme
Hi Ilan,
> I agree that mappedBy should remain in Field. Same is true for indexed,
> unique, deleteAction, sequence and valueStrategy, which can all be
> useful also for object databases. I think that only table, column and
> columns are specific for relational databases. Same is applied also for
Hi Andy,
I agree that mappedBy should remain in Field. Same is true for indexed,
unique, deleteAction, sequence and valueStrategy, which can all be
useful also for object databases. I think that only table, column and
columns are specific for relational databases. Same is applied also for
Elemen
An initial split of JDO and ORM annotations is at :-
JDO :-
http://jpox.cvs.sourceforge.net/jpox/JPOX/Plugins/Java5/src/java/org/jpox/annotations/
ORM:-
http://jpox.cvs.sourceforge.net/jpox/JPOX/Plugins/Java5/src/java/org/jpox/annotations/orm/
Still to do :
@DatastoreIdentity currently has colu
Hi Craig,
> I believe that you cannot map a Calendar to a single column in the
> datastore because Calendar has a few features that you don't want to
> lose:
Thanks. I only had the storage of time and timezone in mind ... ie. part 1,
forgetting the strangeness of Calendar.
Withdraw the request
12 matches
Mail list logo
