mysql - 更改 my.ini 文件上的 datadir 在 WAMP 中不受尊重

Question

我通常不会问这方面的问题，但我正在用这个问题撞墙。我正在尝试设置 WAMP 以与 Dropbox 一起使用。我已经使用了这两个教程(http://mymediamagnet.com/how-to-setup-wamp-with-dropbox/ 和 http://abhisheksachan.blogspot.com/2012/08/web-development-environment-made-easy.html)，因为它们都告诉我同样的事情。

您在 Apache 中所做的 httpd.conf 设置效果很好。我的新 www 文件夹中的所有文件都得到尊重，并在 Dropbox 中的多台计算机之间共享。但是我将数据库文件存储在 Dropbox 中的设置似乎没有得到尊重。

我已经编辑了 my.ini 文件以在 datadir 中包含正确的 Dropbox mysql 文件夹。我已经从这里复制了所有内容:C:\wamp\bin\mysql\mysql5.6.17\data 到这个新的 Dropbox mysql 文件夹。但每次我打开 phpmyadmin 并添加或删除数据库时，它都会在旧的 wamp 文件夹中执行:C:\wamp\bin\mysql\mysql5.6.17\data。

我在这里找到了这个 my.ini 文件:C:\wamp\bin\mysql\mysql5.6.17 所以我知道这是 WAMP 应该使用的文件。我已经尝试通过完全删除它来排除故障，搞砸了文件中的所有数据，但 mysql 只是继续工作并查看旧的数据库文件夹。

所以我唯一的想法是这个配置文件没有得到尊重。顶部有一些说明，我不完全理解这是一个示例文件，但我看到的所有地方都说这就是 wamp 所看到的。所以现在我迷路了，不知道为什么它不起作用。

请帮忙。这是我的整个 my.ini 文件，因为我确定 key 就在其中。

# Example MySQL config file for medium systems.
#
# This is for a system with little memory (32M - 64M) where MySQL plays
# an important part, or systems up to 128M where MySQL is used together with
# other programs (such as a web server)
#
# You can copy this file to
# /etc/my.cnf to set global options,
# mysql-data-dir/my.cnf to set server-specific options (in this
# installation this directory is C:\mysql\data) or
# ~/.my.cnf to set user-specific options.
#
# In this file, you can use all long options that a program supports.
# If you want to know which options a program supports, run the program
# with the "--help" option.

# The following options will be passed to all MySQL clients
[client]
#password   = your_password
port        = 3306
socket      = /tmp/mysql.sock

# Here follows entries for some specific programs

# The MySQL server
[wampmysqld]
port        = 3306
socket      = /tmp/mysql.sock
key_buffer_size = 16M
max_allowed_packet = 1M
sort_buffer_size = 512K
net_buffer_length = 8K
read_buffer_size = 256K
read_rnd_buffer_size = 512K
myisam_sort_buffer_size = 8M
basedir=c:/wamp/bin/mysql/mysql5.6.17
log-error=c:/wamp/logs/mysql.log
datadir=c:/Users/E Money/Dropbox/wamp/mysql

lc-messages-dir=c:/wamp/bin/mysql/mysql5.6.17/share

# Change your locale here !
lc-messages=fr_FR

# Avoid warning
explicit_defaults_for_timestamp = TRUE

# Don't listen on a TCP/IP port at all. This can be a security enhancement,
# if all processes that need to connect to mysqld run on the same host.
# All interaction with mysqld must be made via Unix sockets or named pipes.
# Note that using this option without enabling named pipes on Windows
# (via the "enable-named-pipe" option) will render mysqld useless!
# 
#skip-networking

# Disable Federated by default
skip-federated

# Replication Master Server (default)
# binary logging is required for replication
log-bin=mysql-bin

# binary logging format - mixed recommended
binlog_format=mixed

# required unique id between 1 and 2^32 - 1
# defaults to 1 if master-host is not set
# but will not function as a master if omitted
server-id   = 1

# Replication Slave (comment out master section to use this)


# New for MySQL 5.6 if no slave
skip-slave-start

#
# To configure this host as a replication slave, you can choose between
# two methods :
#
# 1) Use the CHANGE MASTER TO command (fully described in our manual) -
#    the syntax is:
#
#    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>,
#    MASTER_USER=<user>, MASTER_PASSWORD=<password> ;
#
#    where you replace <host>, <user>, <password> by quoted strings and
#    <port> by the master's port number (3306 by default).
#
#    Example:
#
#    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306,
#    MASTER_USER='joe', MASTER_PASSWORD='secret';
#
# OR
#
# 2) Set the variables below. However, in case you choose this method, then
#    start replication for the first time (even unsuccessfully, for example
#    if you mistyped the password in master-password and the slave fails to
#    connect), the slave will create a master.info file, and any later
#    change in this file to the variables' values below will be ignored and
#    overridden by the content of the master.info file, unless you shutdown
#    the slave server, delete master.info and restart the slaver server.
#    For that reason, you may want to leave the lines below untouched
#    (commented) and instead use CHANGE MASTER TO (see above)
#
# required unique id between 2 and 2^32 - 1
# (and different from the master)
# defaults to 2 if master-host is set
# but will not function as a slave if omitted
#server-id       = 2
#
# The replication master for this slave - required
#master-host     =   <hostname>
#
# The username the slave will use for authentication when connecting
# to the master - required
#master-user     =   <username>
#
# The password the slave will authenticate with when connecting to
# the master - required
#master-password =   <password>
#
# The port the master is listening on.
# optional - defaults to 3306
#master-port     =  <port>
#
# binary logging - not required for slaves, but recommended
#log-bin=mysql-bin

# Point the following paths to different dedicated disks
#tmpdir     = /tmp/     
#log-update     = /path-to-dedicated-directory/hostname

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = C:\mysql\data/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = C:\mysql\data/
#innodb_log_arch_dir = C:\mysql\data/
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

[mysqldump]
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash
# Remove the next comment character if you are not familiar with SQL
#safe-updates

[isamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[myisamchk]
key_buffer = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld]
port=3306
explicit_defaults_for_timestamp = TRUE

Answer 1

2.5 版本的 64 位 WAMPServer 有一个小错误

在你的 64 位 my.ini 中改变这个

来自

# The MySQL server
[wampmysqld]

到

# The MySQL server
[wampmysqld64]

这个section header必须匹配MySQL服务器运行的服务名，在64位的WAMPServer上改成了wampmysqld64，但是这个section header被遗忘了。

注意:您不需要运行 64 位 WAMPServer，因为您的操作系统是 Windows 64 位。

事实上 64 位 PHP 还不是一个完整的端口，仍然被认为是“实验性的”

还有相当多的 PHP 扩展还没有转换为 64 位，因此最好继续使用 32 位 WampServer (Apache/MySQL/PHP)，除非您有一些非常具体的需要使用 64 位版本。