| v 1.35 - Inconsistent SQL files [message #1318] |
Mon, 28 April 2008 12:51  |
ljkbrost
Messages: 59
Registered: April 2006
|
Member |
|
|
Hi,
After downloading version 1.35, there is a minor annoyance with the MySQL data files for the Menu. The data was exported with the line "USE menu" which forces the data to be imported into the menu table even if that's not what you want.
For example:
mysql -u root -p radicore_v134_menu < radicore/menu/sql/mysql/menu-scheme.sql
Will create the menu into the database 'radicore_v134_menu'. While
mysql -u root -p radicore_v134_menu < radicore/menu/sql/mysql/menu-data.sql
Will fail or insert data into the wrong table because of the "USE menu" directive in the sql file.
This problem does not happen for the other databases workflow, dict, or audit. It's a minor annoyance as you have to edit the file if you are using databases with prefixes.
Cheers,
Kyle Brost
----
www.softelephant.com
|
|
|
|
|
|
|
|
|
|
| Re: v 1.35 - Inconsistent SQL files [message #1322 is a reply to message #1318] |
Mon, 28 April 2008 15:12  |
AJM
Messages: 2349
Registered: April 2006
Location: Surrey, UK
|
Senior Member |
|
|
If I do not specify the database name then someone complains, but if I put it in then someone else complains. Some people execute the script without specifying a particlar database name because they assume that the script will automatically switch to the correct database, and then complain that it doesn't work.
As it is not possible to know for certain if you are using a prefix with your database names, so the safest option is to leave out the "USE 'xxx';" statement completely. This will mean that everybody will be responsible for identifying the correct database name before executing each script.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
|
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
