Foreign Key Constraint name is not unique for some modeling patterns
--------------------------------------------------------------------

         Key: UMLMETA-70
         URL: http://jira.andromda.org/browse/UMLMETA-70
     Project: UML Metafacades
        Type: Bug

    Versions: 3.0 M3    
    Reporter: Tom
 Assigned to: Wouter Zoons 


The Hibernate Cartridge does not generate unique foreign key constrain names 
for the following modeling pattern.

  1) The "table per concrete class" mapping strategy is used
  2) There are two or more concrete subclasses derived from an abstract class 
that contains an association

A foreign key constraint with the same name is generated for each table mapped 
to a concrete subclass that is derived from an abstract class that contains the 
association.

According to Chad Brandon, the UML metafacades need to be modified to handle 
foreign key generation correctly for this modeling pattern.

-- 
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: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

Reply via email to