Dev:mysql - MySQL Programmer's Manual
However, a number of important assumptions are made when using the default behaviors of the mysql module:
- The local host (127.0.0.1) has a running MySQL server (see below) and is accepting connection on port 3306 (TCP) or the socket /tmp/mysql.sock.
- The user gridlabd has been created on the local host's MySQL server.
- The user gridlabd has no password for client on the local host.
- The user gridlabd has permission to create and administer the schema gridlabd.
- Only one instance of the class database is created.
- Linux and Mac OSX builds
- The MySQL libraries must be installed prior to running ./configure and the libraries must be installed in /usr/local/mysql-connector-c. Because the downloaded files usually include the version number, you should create a symbolic link to the download folder:
host% cd /usr/local host% ln -s mysql-connector-dir mysql-connector-c
- Windows builds
- The libraries must be installed in ;C:\Program Files\MySQL\MySQL Connector C\include. Note that by default the MySQL Connector C installer includes the version number in the path so you should change the install folder to match the above path.
- A schema named gridlabd that is empty.
- A user named gridlabd with ALTER,CREATE,CREATE TEMPORARY TABLES,DELETE,DROP,INDEX,INSERT,LOCK TABLES,REFERENCES,SELECT,UPDATE access to the schema gridlabd with no password from host localhost (do not use the IP address 127.0.0.1). Do not set account limits or any administrative roles for this user.
Note: It is very strongly recommended that you do not use the gridlabd user for any other purpose than testing and validation because the test procedures often include DROP DATABASE commands resulting in total destruction of all data in the gridlabd schema. If you use the NEWDB option on the default schema gridlabd you will get a warning such as
WARNING [INIT] : database:0 users NEWDB option on the default schema 'gridlabd' - this is extremely risky
but that's all you get before the deed is done. Obviously, autotests are expected to produce this warning because they typically use NEWDB on the default schema.