openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Leung (JIRA)" <>
Subject [jira] [Commented] (OPENJPA-2358) openjpa-maven-plugin generates wrong sql for derby
Date Fri, 12 Apr 2013 01:53:16 GMT


Ted Leung commented on OPENJPA-2358:

I can't seem to find any information on how to set entity manager properties from the openjpa-maven-plugin.

Do you happen to know off hand?

if not, no worries, I'm just running it with out the constraint right now as my work around.
> openjpa-maven-plugin generates wrong sql for derby
> --------------------------------------------------
>                 Key: OPENJPA-2358
>                 URL:
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: tooling
>    Affects Versions: 2.2.1
>         Environment: linux (fedora 16, x86_64), oracle jdk 1.7.0_17-b02, Maven 3.0.5,
>            Reporter: Ted Leung
>         Attachments: openjpa_derby_test.tar.gz
> model object fields are not defaulting to allow null, even when I explicity set @Column(nullable=true),
it still generates the columns as "not null".
> As an example :
> @Column(nullable = true, length = 128)
> private String dataType;
> results in generated sql of :
> dataType VARCHAR(128) NOT NULL
> This happens for both org.apache.derby.jdbc.ClientDriver, and org.apache.derby.jdbc.EmbeddedDriver.
As a test, I changed the driver to the MySql driver and everything worked as expected so I'm
fairly sure this is not a configuration / setup issue unless there's special configuration
required for derby.

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

View raw message