|
From: SourceForge.net <no...@so...> - 2006-06-19 19:05:35
|
Patches item #1299109, was opened at 2005-09-22 13:46 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1299109&group_id=74338 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: Accepted Priority: 5 Submitted By: Andy Dustman (adustman) Assigned to: Nobody/Anonymous (nobody) Summary: Support FOREIGN KEY for MySQL Initial Comment: MySQL supports the full FOREIGN KEY syntax in versions 3.23.50 and newer, and 4.0.8 and newer, and I believe all 4.1 and 5.0 versions. To implement this in SQLObject-0.7a, I copied the col.SOForeignKey.postgresCreateSQL() method to mysqlCreateSQL() and performed some minor editing. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2006-06-19 12:05 Message: Logged In: NO I had the same problem and fixed it almost the same way as the bug reporter, and it worked. I think this patch should be included as soon as possible. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2005-10-23 06:28 Message: Logged In: YES user_id=4799 Applied at the revision 1135 in the trunk. ---------------------------------------------------------------------- Comment By: Oleg Broytmann (phd) Date: 2005-09-23 07:17 Message: Logged In: YES user_id=4799 Looks good at first glance, but I am reluctant to apply such a patch while SQLObject is at the beta stage, espcially considering I use Postgres and MySQL, but not MySQL, so I cannot properly test it. Let's wait until post-0.7. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=540674&aid=1299109&group_id=74338 |
