[jira] [Updated] (OPENJPA-2358) openjpa-maven-plugin generates wrong sql for derby

["Ted Leung (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPENJPA-2358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ted Leung updated OPENJPA-2358:
-------------------------------

    Attachment: openjpa_derby_test.tar.gz

test project using maven
                
> openjpa-maven-plugin generates wrong sql for derby
> --------------------------------------------------
>
>                 Key: OPENJPA-2358
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2358
>             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, derby 10.9.1.0
>            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: http://www.atlassian.com/software/jira