Bug #12084 Update temporary tables withe respect to foreign keys
| Submitted: | 21 Jul 2005 15:22 | Modified: | 8 Sep 2005 20:20 |
|---|---|---|---|
| Reporter: | Jason Pyeron | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
| Version: | 4.1.13 | OS: | Windows (w2k) |
| Assigned to: | Osku Salerma | CPU Architecture: | Any |
[21 Jul 2005 15:22]
Jason Pyeron
[21 Jul 2005 17:33]
Heikki Tuuri
Hmm... InnoDB should return an error in this case, if the foreign key really does not work. Assigning this to Marko Mäkelä. Regards, Heikki
[21 Jul 2005 18:16]
Jorge del Conde
Thanks for your bug report.
[21 Jul 2005 19:29]
Jason Pyeron
no, no error please. the foriegn keys should work, without the error, my software will work now, and later. since my software wonth violate the key constraints, and the table only exists during its connection then no harm no foul. just need to fix the aliasing issue so the keys are used.
[6 Sep 2005 11:38]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/29361
[6 Sep 2005 13:08]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/29368
[8 Sep 2005 9:33]
Osku Salerma
Pushed to 5.0.13 and 5.1.
[8 Sep 2005 20:20]
Paul DuBois
Noted in 5.0.13, 5.1.2 changelogs.
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.066 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.