Bug #1445 Windows servers: The Unkept Promise
Submitted: 30 Sep 2003 9:49 Modified: 10 Dec 2003 18:49
Reporter: Paul Dubois Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.0.15, at least OS:Microsoft Windows (Windows)
Assigned to: MySQL Verification Team CPU Architecture:Any

[30 Sep 2003 9:49] Paul Dubois
Database directory symlinking on Windows is supported
only by the -max servers, mysqld-max and mysql-max-nt.
However, all the Windows servers seem to promise this
capability, because they uniformly respond YES to the
query SHOW VARIABLES LIKE 'have_symlink'.

For mysqld and mysqld-nt, this amounts to a promise
that is not kept, because they don't really process symlinks
properly.  The symlinked database shows up in the output
of SHOW DATABASES, but both USE db_name and SHOW
TABLES FROM db_name fail.

I would guess for mysqld and mysqld-nt, the value for
have_symlink should be NO?

How to repeat:
Symlink a database directory, then start either mysqld
or mysqld-nt.  Then try to use the database with USE
db_name or SHOW TABLES FROM db_name.
[30 Sep 2003 9:50] Paul Dubois
Forgot to fill in OS field.
[30 Sep 2003 10:10] MySQL Verification Team
Paul, this was fixed in some releases early, so the VC++ project
files has missed the sets for to enable the symlink for all the
servers. I am assigned Greg for to enable it again for the 
all VC++ projects files.
[30 Sep 2003 10:11] MySQL Verification Team
Sorry I forgot to mark verified.
[30 Sep 2003 10:28] Paul Dubois
Miiguel, does this mean that all Windows servers then
should support database symlinking, not just the -max
[30 Sep 2003 11:37] MySQL Verification Team
Yes Paul all the servers besides the -max ones, as I said before this
was already introduced and missed for unknown reason.
[10 Dec 2003 18:49] Michael Widenius
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

This was fixed some time ago