Ok, done but with the same result
--
View this message in context:
http://openjpa.208410.n2.nabble.com/element-column-of-the-associated-table-is-null-tp7498933p7502522.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
Can you create a small unit test that exhibits this behavior? My test that
I put together yesterday worked as expected.
Thanks,
Rick
On Thu, Apr 26, 2012 at 6:22 AM, CarpathianAnonymous
andreibratu2...@yahoo.com wrote:
Ok, done but with the same result
--
*Rick Curtis*
Rick,
If I wrap the reserved word in quotes (\...\), then the column is
created correctly. Here is the generated create table sql:
CREATE TABLE xxx (guid BIGINT NOT NULL, approved BOOL, grant VARCHAR(64),
PRIMARY KEY (guid));
Yet, when I try to persist to that table, OpenJPA runs an alter
I've attached my UnitTest
http://openjpa.208410.n2.nabble.com/file/n7503208/src.rar src.rar
--
View this message in context:
http://openjpa.208410.n2.nabble.com/element-column-of-the-associated-table-is-null-tp7498933p7503208.html
Sent from the OpenJPA Users mailing list archive at Nabble.com.
It appears that this in an OpenJPA bug. Could I have you open a JIRA for
this issue and attach your testcase?
I'm not sure when I'll get time to try to fix this issue, but for the short
term you have a couple workaround optionsOption #1 -- you could change
your ID generation strategy to
Jason --
I'm able to recreate your failure when running against MySQL and a hacked
up runtime. Can you try running with the following property[1] set ?
Thanks,
Rick
[1] property name=openjpa.jdbc.DBDictionary
value=postgres(supportsDelimitedIdentifiers=false)/
On Thu, Apr 26, 2012 at 10:03 AM,
