openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Dick (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1651) Unique colums automatically defined as non-nullable (part 2)
Date Wed, 05 May 2010 15:49:02 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864371#action_12864371
] 

Michael Dick commented on OPENJPA-1651:
---------------------------------------

Re posting Mark's comments :
A few tips on my sample project: 
The NOT NULL can be checked by simply executing 
$> mvn openjpa:sql 
which generates the database creation SQL script in 
./target/database.sql 

to execute the project you need to create the database upfront in MySQL with 
create database TestDb; 
user 'root' with no password is assumed (persistence.xml) 

After 
$> mvn clean install 
you will see the myString column as empty string instead of NULL when doing a 
mysql> select * from NullFieldTable; 
+----+----------+ 
| PK | myString | 
+----+----------+ 
| 1 | | 
+----+----------+ 
1 row in set (0.00 sec) 

> Unique colums automatically defined as non-nullable (part 2)
> ------------------------------------------------------------
>
>                 Key: OPENJPA-1651
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1651
>             Project: OpenJPA
>          Issue Type: Bug
>            Reporter: Mark Struberg
>         Attachments: openjpa-test.zip
>
>
> Continuing the discussion from OPENJPA-1387. The original issue was closed and marked
as shipped in OpenJPA 2.0.0 (one of the betas) - it should not appear in 2.0.1 as well - thus
the need for a new issue. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message