[ http://jira.andromda.org/browse/UMLMETA-29?page=history ]
Chad Brandon closed UMLMETA-29:
-------------------------------
Resolution: Fixed
Fix Version: 3.0 RC2
I added a "defaultMultiplicity" namespace property, you can use 0 or 1 to
configure it. 0 means optional (not-null in terms of entities) 1 required (1
is the default).
> Default Nullability for Hibernate/Database constraints
> ------------------------------------------------------
>
> Key: UMLMETA-29
> URL: http://jira.andromda.org/browse/UMLMETA-29
> Project: UML Metafacades
> Type: Improvement
> Environment: andromda rc1
> Reporter: Darius Schier
> Assignee: Chad Brandon
> Fix For: 3.0 RC2
>
> Darius Schier wrote:
> > Hi there!
> >
> > Is there any namespace property that defines how nullability is
> > handeled if no multiplicity is given for an attribute?
> >
> > Default seems to be that all attributes are defined as not-null=true
> > within hibernate.hbm if they do not have an explicit multiplicity of
> > [0..1].
> >
> > Usually there are much more columns that could be NULL
> >
> No, but there should probably be one, please file a jira issue under the UML
> Metafacades project.
> >
> >
> > Best Regards
> >
> > Darius
> >
> >
> >
--
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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel
