Setting prototype to id for a primary changes relationship mandatory status on other tables where it is a foreign key
---------------------------------------------------------------------------------------------------------------------
Key: WOL-914
URL: http://issues.objectstyle.org/jira/browse/WOL-914
Project: WOProject/WOLips
Issue Type: Bug
Components: wolips
Affects Versions: WOLips planning
Environment: wolips 5543, eclipse 3.4.1, webobjects 5.3.3, mac os x 10.4.11, mac book pro, mysql 5, wonder 5.0.0.8529
Reporter: D Tim Cummings
I have a MySQL model without prototypes. Example
Table TblOne
idOne INT (Primary key)
strOne VARCHAR 255
Table TblTwo
idTwo INT (Primary key)
idOne INT (Foreign key to TblOne) Nulls allowed
toTblOne = optional relationship to TblOne using foreign key idOne
Table TblThree
idThree INT (Primary key)
idOne INT (Foreign key to TblOne) Nulls allowed
toTblOne = optional relationship to TblOne using foreign key idOne
When I edit TblOne and give the primary key idOne the prototype "id" and save my model, the plist files for TblTwo and TblThree are modified by entity modeler to make the relationships toTblOne mandatory. The correct behaviour would be for TblTwo.plist and TblThree.plist to be left unchanged.
-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.objectstyle.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
This archive was generated by hypermail 2.0.0 : Thu Nov 13 2008 - 23:08:27 EST