[ http://jira.andromda.org/browse/EJB-56?page=comments#action_14440 ]
Roland Burgermann commented on EJB-56: -------------------------------------- I think it's only necessary to remove the NOT NULL, because set of multiplicity to [1] will result actually in a sql code like "VARCHAR(20) NOT NULL not null". This codepart cannot proceed on an Oracle database: ORA-02258: duplicate or conflicting NULL and/or NOT NULL specifications But i'm not sure, if this will work for every circumstance. > Multiplicity is ignored during code generation of Enumeration type entity > attributes > ------------------------------------------------------------------------------------ > > Key: EJB-56 > URL: http://jira.andromda.org/browse/EJB-56 > Project: EJB Cartridge > Type: Bug > Environment: WinXP Pro, andromda-3.2, ejb3-1.0-SNAPSHOT > Reporter: heapifyman > Assignee: Vance Karimi > Priority: Minor > > Setting an entity bean's attribute type to an Enumeration, using literals, > and setting Multiplicity for that attribute to [0...1], the Multiplicity is > ignored during code generation and the columnDefinition is always set to: > definition = "VARCHAR(" + length + ") NOT NULL"; > Workaround for [0...1]: > Set the @andromda.persistence.column.definition tagged value for that > attribut to "VARCHAR(<MAX_LENGHT_OF_YOUR_ENUMERATION_LITERALS>)" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.andromda.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
