[dna-issues] [JBoss JIRA] Commented: (DNA-520) DNA w/ JPA/Oracle - bad create table DNA_OPTIONS

Fri Sep 11 14:57:23 EDT 2009

    [ https://jira.jboss.org/jira/browse/DNA-520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12485407#action_12485407 ] 

Randall Hauch commented on DNA-520:
-----------------------------------

Ah, you are correct.  The "unique=true" parameter is actually unnecessary since the column is already a primary key since it is annotated with @Id.  I guess the Oracle is just pretty strict about this.  Removing the parameter didn't seem to cause any other problems.

> DNA w/ JPA/Oracle - bad create table DNA_OPTIONS 
> -------------------------------------------------
>
>                 Key: DNA-520
>                 URL: https://jira.jboss.org/jira/browse/DNA-520
>             Project: DNA
>          Issue Type: Bug
>         Environment: Oracle 10g
> JBoss AS 5.1
> JDK6
>            Reporter: John Ament
>            Assignee: Randall Hauch
>
> The create table generated for DNA_OPTIONS is
> create table DNA_OPTIONS (NAME varchar2(512 char) not null unique, VALUE varchar2(512 char) not null, primary key (NAME))
> However, to work correctly in Oracle, it should be:
> create table DNA_OPTIONS (NAME varchar2(512 char) not null, VALUE varchar2(512 char) not null, primary key (NAME))
> which means we have to remove the unique=true attribute from dna options entity.
> There may be another entity like this as well, will double check.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira