Bug #17623 InnoDB innodb_file_per_table symlink crash XP

• Submitted: 21 Feb 2006 16:39
• Modified: 22 Feb 2006 0:57
• Reporter: [ name withheld ]
• Status: Duplicate
• Category: MySQL Server: InnoDB storage engine
• Severity: S1 (Critical)
• Version: 5.0.18
• OS: Windows (XP)
• CPU Architecture: Any

[21 Feb 2006 16:39] [ name withheld ]

Description:
1) on XP running mysqld-max-nt and MySQL 5.0.18 enable innodb_file_per_table 
2) create mylink.sym pointing wherever you want, try to create an InnoDB table in database mylink, for example mytable
3) the mytable.frm file is created and then the server crashes before creating mytable.ibd

the issue has been raised before and is similar to others concerning the possibility of specifying the location of db files with InnoDB. in my case the reason for doing this is that i want (on XP) to have a small DB on an external usb disk which can be physically removed for privacy/security reasons. InnoDb tables are required to be able to enforce foreign keys (not supported by myisam as far as i know)

How to repeat:
1) on XP running mysqld-max-nt and MySQL 5.0.18 enable innodb_file_per_table 
2) create mylink.sym pointing wherever you want, try to create an InnoDB table in database mylink, for example mytable
3) the mytable.frm file is created and then the server crashes before creating mytable.ibd

[21 Feb 2006 16:50] Heikki Tuuri

This is probably a duplicate of:

http://bugs.mysql.com/bug.php?id=11894

Regards,

Heikki

[22 Feb 2006 0:57] [ name withheld ]

I agree that the bug is a duplicate, however since the old submission is 6 months old and the bug was propagated from 4.1 to 5.0, i thought it was appropriate to point out the propagation. Is a fix planned? when?
is some sort of workaround available/planned?

[22 Feb 2006 1:12] MySQL Verification Team

Bug: http://bugs.mysql.com/bug.php?id=11894 was already
edited mentioning this it is a duplicate. I am adding the
version 5.0 as version affected. Thank you for the feedback.