You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2010/05/05 17:49:02 UTC
[jira] Commented: (OPENJPA-1651) Unique colums automatically
defined as non-nullable (part 2)
[ 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.