We finally where able to use Oracle, we've put some docs online howto
configure JPA in our Spring enabled configuration, maybe useful for
others:
http://code.google.com/p/openmeetings/wiki/Configuration_Oracle
Sebastian
2011/11/2 seba.wag...@gmail.com seba.wag...@gmail.com:
Thanks Miłosz,
I
Thanks for sharing the documentation, one comment for you though... Please
reconsider listing RuntimeUnenhancedClasses as a recommended configuration.
We don't recommend using that feature as it has numerous problems.
Thanks,
Rick
On Thu, Dec 1, 2011 at 3:19 AM, seba.wag...@gmail.com
Thanks Miłosz,
I will try it out and come back with the results!
Thanks
Sebastian
2011/10/25 Miłosz Tylenda mtyle...@o2.pl
Sebastian,
For the sequence name too long problem, you could try setting the
maxAutoAssignNameLength dictionary property to the maximum sequence name
length in
Sebastian,
For the sequence name too long problem, you could try setting the
maxAutoAssignNameLength dictionary property to the maximum sequence name length
in Oracle.
You can also set the sequence name via the autoAssignSequenceName dictionary
property but in this case you will rather need
Hi,
we are still trying to figure out what is going wrong with Oracle and openJPA.
Our configuration now looks like that:
properties
property
name=openjpa.RuntimeUnenhancedClasses value=unsupported/
property
Or let me re-phrase my question:
Is there a possibility to define an alternative name for the sequence
or a table when you are using the option:
property name=openjpa.jdbc.DBDictionary
value=oracle(UseTriggersForAutoAssign=true,BatchLimit=100) /
Or is it really required at this point to rename
The guys from Oracle do (a bit offensive) argue that for such reasons
sequences do exist.
https://forums.oracle.com/forums/thread.jspa?messageID=9909360#9909360
Quote:
Oracle has *sequences* for this purpose.
They are either directly used in an INSERT statement, or assigned to a
column by means
Hi,
when using Oracle 11g with openJPA I do get the following warning while the
tables are populated by openJPA:
Oracle does not support auto-assigne d column values. The column may not
behave as desired.
... and the effect is obviously that, as soon as you try to add a new column
with a null
