continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wendy Smoak (JIRA)" <>
Subject [jira] Commented: (CONTINUUM-1662) Store and Data Access tier rework
Date Wed, 09 Sep 2009 21:28:31 GMT


Wendy Smoak commented on CONTINUUM-1662:

Wiki page contents:  

Database access
In the actual store, we have few issues with JPox and database mapping:

long string aren't stored correctly in some database like Oracle due to small length of the
Oracle varchar
we have some issues with relations between objects during update/delete actions of some entities
we have some memory issues due to lot of datas from entities loaded that we don't really need
For all of that and more, I want to rewrite all the database access from scratch. To do this,
I want to use JPA (with OpenJPA or Toplink). I choose JPA instead of JPOX or something else
because :

it is very easy to develop/maintain the data access code
it is customizable for optimization by query overwrite and some query hints defined externally
the SQL for the schema generation can be generated for each database, so customizable by users
it is the new standard that I like and recommend 
Personally, I'd prefer Toplink because it is the reference implementation and it is already
used by lot of users, I don't know about OpenJPA. We must look at the Toplink license for
the compatibility with the ASL.


If there is interest in this it would probably be best to discuss it on the dev list and open
a more specific issue.

> Store and Data Access tier rework
> ---------------------------------
>                 Key: CONTINUUM-1662
>                 URL:
>             Project: Continuum
>          Issue Type: Task
>            Reporter: Rahul Thakur
> Please refer to details here:

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message