MySQL 5.x

When we use GUI tools like HeidiSQL with MySQL Windows binaries - setup from MySQL.com might be creating issues like these. Because recently faced errors #1364 and #1133 both became visible while I did clean install of MySQL by downloading Windows Installer for MySQL 5.5.8 from MySQL.com and not while using it with MySQL as part of some WAMP package.

It must be because the way some parameters come as defaults while we use MySQL installer or might be the way we configure the MySQL Instance using MySQL instance configuration wizard.

SQL Error (1133): Can't find any matching row in the user table

Now we will get above error message due to SQL_MODE variable value set to NO_AUTO_CREATE_USER, you can check value for your server's sql-mode by using following SQL:

SHOW VARIABLES LIKE 'SQL_MODE'
 

Output can be something like STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION as we can specify multiple values separated by comma. NO_AUTO_CREATE_USER won't let you create users with empty passwords.

Prevent the GRANT statement from automatically creating new users if it would otherwise do so, unless a nonempty password also is specified. (Added in MySQL 5.0.2)

If you're using HeidiSQL 6 or earlier you won't be able to create users even if you specify password due to the way HeidiSQL constructs the SQL to create user. See the screen-shot:

MySQL Error 1133: While Creating New User

Solution: There are 3 ways to fix this.

A) Download latest version if you're using HeidiSQL and facing this problem with HeidiSQL.

B) Change SQL_MODE if you can't change your tool or SQL statement syntax somehow. You can either set it for SESSION if you want to fix it for a while and get away with it for now.

C) Use SQL similar to below:

CREATE USER 'digitss'@'localhost' IDENTIFIED BY 'digitss';
GRANT EXECUTE, PROCESS, SELECT, SHOW DATABASES, SHOW VIEW, ALTER, ALTER ROUTINE, CREATE, CREATE ROUTINE, CREATE TEMPORARY TABLES, CREATE VIEW, DELETE, DROP, EVENT, INDEX, INSERT, REFERENCES, TRIGGER, UPDATE, CREATE USER, FILE, LOCK TABLES, RELOAD, REPLICATION CLIENT, REPLICATION SLAVE, SHUTDOWN, SUPER ON *.* TO 'digitss'@'localhost' WITH GRANT OPTION;
 

Basically earlier version of HeidiSQL had different order for above SQL command.Similar Posts:

• MySQL 5.5.8 – Problem while Creating new User (SQL Error (1364): Field ‘authentication_string’ doesn’t have a default value)
• HeidiSQL 5.1 – good has got better
• HeidiSQL 4.0 RC1 released
• backup/restore MySQL db using MYSQLDUMP (quick reference)
• Top free / open-source tools for MySQL Development / Administration

MySQL 5.5.8

I have just downloaded and setup MySQL 5.5.8 community server for Windows (32bit Installer) from MySQL official downloads. After downloading while I tried connecting it with HeidiSQL 5.x I got following error "Problem while Creating new User (SQL Error (1364): Field 'authentication_string' doesn't have a default value)".

It seems like it's a problem with HeidiSQL-5, probably due to the fact that table schema for mysql.users table might be changed in MySQL 5.5.8. You might see something like following if you're using HeidiSQL-5.

MySQL5.5 > Create User error while using HeidiSQL 5.0

ALTER TABLE `user`  CHANGE COLUMN `authentication_string` `authentication_string` TEXT NULL COLLATE 'utf8_bin' AFTER `plugin`;
 

If you have encountered any bumps on the road while upgrading to MySQL 5.5, please do share with us.Similar Posts:

• MySQL5 Problem while creating new user – SQL Error (1133): Can’t find any matching row in the user table
• HeidiSQL 4.0 RC1 released
• HeidiSQL 5.1 – good has got better
• Top free / open-source tools for MySQL Development / Administration
• Using Views to avoid cross database connection – MySQL

Views - Image courtesy Flickr

CREATE TABLE `contacts` (
	`id` INT(10) NOT NULL AUTO_INCREMENT,
	`first_name` VARCHAR(100) NOT NULL,
	`last_name` VARCHAR(100) NOT NULL,
	`email` VARCHAR(100) NULL DEFAULT NULL,
	`cell_phone` VARCHAR(25) NULL DEFAULT NULL,
	`home_phone` VARCHAR(25) NULL DEFAULT NULL,
	`note` VARCHAR(255) NULL DEFAULT NULL,
	PRIMARY KEY (`id`)
)
ENGINE=MyISAM
ROW_FORMAT=DEFAULT;
 

And you can create your view in "another_db" database with following syntax:

SELECT * FROM `my_db`.`contacts`
 

View definition will be updated to following automatically:

SELECT `my_db`.`contacts`.`id` AS `id`,`my_db`.`contacts`.`first_name` AS `first_name`,`my_db`.`contacts`.`last_name` AS `last_name`,`my_db`.`contacts`.`email` AS `email`,`my_db`.`contacts`.`cell_phone` AS `cell_phone`,`my_db`.`contacts`.`home_phone` AS `home_phone`,`my_db`.`contacts`.`note` AS `note` FROM `my_db`.`contacts`
 

That's it we are done.
Now we can execute any Insert, Update or Select query on this view, which will in turn change data in "mydb.contacts" table.

This can be a simpler solution if we want to avoid dealing with handling multiple database in PHP or any other server-side programming language.

INSERT INTO `v_contacts` (`first_name`, `last_name`, `email`, `cell_phone`, `note`) VALUES ('Bill', 'Gates', 'bill@msn.com', '7188802201', 'Former Microsoft CEO');
 

This is not something new; we knew and we read this all while we were at college. But it makes us feel good if we can put something like this at work which can be a small thing but can help us saving some time..!

Friends, comment if you liked this post, or share your experiences.Similar Posts:

• Possible Sybase SQL Anywhere bug
• MySQL 5.5.8 – Problem while Creating new User (SQL Error (1364): Field ‘authentication_string’ doesn’t have a default value)
• HeidiSQL 5.1 – good has got better
• Printing data table vertically..! Why? and How?
• Alternate to FIND_IN_SET for non-MySQL databases

HeidiSQL

HeidiSQL has been excellent SQL Administration and Development tool so far for me. HeidiSQL has active development team which keeps adding new feature and upgrading and correcting bugs to get us the great tool for MySQL development.

I have been using HeidiSQL since more than three and half years now and I am really happy with it. I must say that we work with heavy database consisting of more than 400 tables and database size exceeding few GBs but HeidiSQL has never let us down. I have tried loading my development database with phpMyAdmin and SQL Buddy both but they just failed to load such a large database with few hundreds of tables..! But with HeidiSQL I never had any problem except I got some crashing sometime in newer 5.x version but I am sure all such things will be fixed in coming builds. I am not telling that there are no other good tools are available in the market but HeidiSQL is in premium open-source tool at free of cost. I remember I had written a post on HeidiSQL 4.x more than a year ago and today we are up with HeidiSQL 5.1.

HeidiSQL 5.1 Interface

New Features with HeidiSQL 5.x are:

• Improved UI and design: better, handy interface to edit table structure, indexes, fields - most of routine tasks are at almost 1 or 2 clicks.
• Improved Stored Procedure, Trigger and new Event support: Trigger and Stored routine support has improved while new support for MySQL Events are added..!
• Excellent MySQL User Management: User Management support has been good which has improved.
• Multiple Query tabs: This feature was one of my much awaited feature. I am loving it.:) Bunch of Thanks HeidiSQL Team for this..!
• Copy selected Rows as SQL: You can go to table data view, filter data by your custom criteria and out of that you can select N rows and export as SQL, CSV, XML or HTML. I really like this Copy selected rows as SQL. Excellent and real quick.
• Improved Data Filter, Export and Find features.

Above listed features are what I have observed and I liked during my usage of HeidiSQL 5.x there might be few or more which I might have missed out...! I am sure if you are not using HeidiSQL so far and if you will give it a try you will not leave it for sure.

HeidiSQL fueatures as defined in ReadMe

HeidiSQL is an easy-to-use interface and a "working-horse" for web-developers
using the popular MySQL-Database. It allows you to manage and browse your
databases and tables from an intuitive Windows® interface.

With HeidiSQL you will also be able to
* Generate nice SQL-exports
* Synchronize tables between two databases
* Manage user-privileges
* Import text-files
* Export table-data as CSV, HTML, XML and SQL
* Browse and edit table-data using a comfortable grid
* Create and edit tables, views, stored routines and triggers
* Bulk edit tables (move to db, change engine, collation etc.)
* Batch-insert ascii or binary files into tables
* Write queries with customizable syntax-highlighting and code-completion
* Pretty reformat disordered SQL
* Monitor and kill client-processes
* Connect to servers via commandline
* Find specific text in all tables of all databases of one server
* Optimize and repair tables in a batch manner
* And much more

You can browse through HeidiSQL 5.1 screenshots on official website to take a look at what's new and what is being offered or just download to try.

With this post I would like to appreciate and thanks HeidiSQL team for great work. Thanks Team.Similar Posts:

• HeidiSQL 4.0 RC1 released
• Top free / open-source tools for MySQL Development / Administration
• backup/restore MySQL db using MYSQLDUMP (quick reference)
• MySQL5 Problem while creating new user – SQL Error (1133): Can’t find any matching row in the user table
• Netbeans 7.0 RC1 Released

Let's see how?

Exporting data as CSV file directly using simple MySQL Query

Simply add INTO OUTFILE [FILE_PATH] in your query and you are done. Here is a simple example:

SELECT * FROM [TABLE]
INTO OUTFILE 'X:/[FILE]'

Above statement uses default options for file export of result set of a query, but it is simple to override them. By default file will be TAB DELIMITED file. We can always override as showed in example below:

SELECT * FROM  [TABLE] INTO OUTFILE 'X:/[FILE]'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
LINES TERMINATED BY '\n'

OR

SELECT * INTO OUTFILE 'X:/[FILE]'
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
LINES TERMINATED BY '\n'
FROM  [TABLE]

The beauty is it don't really matter where you place FROM TABLE clause, any of the style would work from above example. Don't forget that we can use all our complex join or where conditions which we really use with SELECT.

Full Syntex:

SELECT
[ALL | DISTINCT | DISTINCTROW ]
[HIGH_PRIORITY]
[STRAIGHT_JOIN]
[SQL_SMALL_RESULT] [SQL_BIG_RESULT] [SQL_BUFFER_RESULT]
[SQL_CACHE | SQL_NO_CACHE] [SQL_CALC_FOUND_ROWS]
select_expr [, select_expr ...]
[FROM table_references
[WHERE where_condition]
[GROUP BY {col_name | expr | position}
[ASC | DESC], ... [WITH ROLLUP]]
[HAVING where_condition]
[ORDER BY {col_name | expr | position}
[ASC | DESC], ...]
[LIMIT {[offset,] row_count | row_count OFFSET offset}]
[PROCEDURE procedure_name(argument_list)]
[INTO OUTFILE 'file_name' export_options
| INTO DUMPFILE 'file_name'
| INTO var_name [, var_name]]
[FOR UPDATE | LOCK IN SHARE MODE]]

Importing data from CSV file directly using simple MySQL Query

Here is the simplest way to do it:

LOAD DATA INFILE 'X:/[FILE]'
INTO TABLE [TABLE]

Similar to Export option of MySQL it will expect file to be TAB DELIMITED if we don't specify any option for it in it's simplest form. So if you simple EXPORT file without any custom specification as a first query example it would simple LOAD DATA from that file, but if you have a file with custom separator than it needs to be specified.

LOAD DATA INFILE 'X:/[FILE]'
INTO TABLE [TABLE]
FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '"'
LINES TERMINATED BY '\n'

Full syntex:

LOAD DATA [LOW_PRIORITY | CONCURRENT] [LOCAL] INFILE 'file_name'
[REPLACE | IGNORE]
INTO TABLE tbl_name
[CHARACTER SET charset_name]
[{FIELDS | COLUMNS}
[TERMINATED BY 'string']
[[OPTIONALLY] ENCLOSED BY 'char']
[ESCAPED BY 'char']
]
[LINES
[STARTING BY 'string']
[TERMINATED BY 'string']
]
[IGNORE number LINES]
[(col_name_or_user_var,...)]
[SET col_name = expr,...]

So exporting and importing data from MySQL seems quite easy and we do not need to write any programming statement to format them just a simple query can do it.

References: (For more reference please refer)
http://dev.mysql.com/doc/refman/5.0/en/select.html
http://dev.mysql.com/doc/refman/5.1/en/load-data.htmlSimilar Posts:

• HeidiSQL 5.1 – good has got better
• Using Views to avoid cross database connection – MySQL
• HeidiSQL 4.0 RC1 released
• Alternate to FIND_IN_SET for non-MySQL databases
• MySQL 5.5.8 – Problem while Creating new User (SQL Error (1364): Field ‘authentication_string’ doesn’t have a default value)

Commands are very quick simple and easy to execute and can be made automated by a PHP or other script/tool.

How to backup using mysqldump?:

Before you use any of commands you have to move to mysql/bin directory of your MySQL installation and MySQL server should be up and running.

To backup all MySQL database on a server:

mysqldump --user=[USER] --password=[PASSWORD] -A > C:/BACKUP_PATH/BACKUP_TIMESTAMP.SQL

To backup specific MySQL database on a server:

mysqldump --user=[USER] --password=[PASSWORD] [DATABASE] > C:/BACKUP_PATH/BACKUP_TIMESTAMP.SQL

To backup certain tables in a MySQL database:

mysqldump --user=[USER] --password=[PASSWORD] [DATABASE] --tables [TABLE_1] [TABLE_2] > C:/BACKUP_PATH/BACKUP_TIMESTAMP.SQL

How to restore database/tables which are backed-up using mysqldump?

Reach to mysql/bin directory on prompt and type in following command with correct backup file created with mysqldump utility and specify database to which you want dump-file SQL statements to be executed.

mysql --user=[USER] --password=[PASSWORD] [DATABASE] < C:/BACKUP_PATH/BACKUP_TIMESTAMP.SQL

So easy and simple just specify database/tables along with connection credentials and use ">" and "<" (in and out) signs in a correct way and you are done.

In my projects we have to deal with exporting system/meta data sync with production server on a regular basis and this seems to be easier than using utilities provided by GUI tools, be it HeidiSQL, PHPMySQL, SQLYog or anything else. Though it depends on project to project and person to person but many times when we have to restore big backup created with HeidiSQL or SQLYog I have seen programs/database exhausted such that increasing packet size won't help either. But mysqldump/mysql restore always been a piece of cake to walk with.

For complete list of parameters of mysqldump please refer: http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html
For mysqlhotcopy reference please refer: http://dev.mysql.com/doc/refman/5.0/en/mysqlhotcopy.htmlSimilar Posts:

• MySQL5 Problem while creating new user – SQL Error (1133): Can’t find any matching row in the user table
• HeidiSQL 5.1 – good has got better
• Top free / open-source tools for MySQL Development / Administration
• HeidiSQL 4.0 RC1 released
• Using Views to avoid cross database connection – MySQL

I have been using HeidiSQL tool for my php/mySQL development for a while now. (more than a year and half..!). Before few months I have upgraded to newer version of HeidiSQL which is 4.1 RC1. It has got quite new and exciting features, looks and skins are improved.

The Good has got better...

1. Better UI:

As we can see in the image below that HeidiSQL 4.0 is packed with new icon set. Size of each database and tables are being displayed just next to object name in the left panel.
Also shows up database objects size next to objects (tables, databases).

New UI/Skin and icon-set

2. Type In Search for Variables, Status and Process List:

Type in Search for Variables, Status and Process List

We can search through system variable from the list on the fly and at the same time by just double clicking on it.

Edit Variables on the fly

3. Improved Filter and Filter Editor:

New and Improved Data Filter editor

As we can see data filter has improved and we can see and edit that filter to anything manually. In previous versions it was just filtering data on all table columns and we didn't have any control on modifying those filter but now we can filter data on completely custom conditions. We just need to specify conditions we use after <WHERE> clause.

We can save applied filter by saving that "Perspective" and specifying appropriate name for it, so that we can revert back to that view of data anytime in future.

4. Better User Management control:

User authentication and privilage control has improved and we can provide rights very easily till column level for any the object of any database.

User Manager

We can pick what rights a User can have and at the same time multi-table / column rights on multiple db and all that with variety of rights on each table or it's column.

Extended User Management

5. Export Data:

Export Tables/Data

Export with different type of Compatibility options.

What is bad/missing?

1. Speed:
While dealing with database with hundreds of tables and size reaching few hundred megabytes it seems to be slower than commercial competitor like Navicat. Although Navicat seems to be falling behind in user interface but works faster than HeidiSQL. Not sure what is keeping Heidi behind in this matter.

2. Export/Import:
Export and Import needs to be improved while dealing with bulk of data. As many a times extended SQL export creates problem while importing. MySQL Dump work faster comparatively;

3. Support for Stored Procedures / Triggers / Functions:
Looking desperately to get support for Stored Procedures, Triggers, Functions. Although Toad for MySQL is there but it seems bit more heavy and HeidiSQL is so lightweight to play with.

4. Inline data editing while Querying data:
In 3.x versions of HeidiSQL it was possible to edit data from query result-set itself but now you have to go and filter data from filter tab itself. Even in Data tab now it asks for confirmation although it is to make sure users don't mess up data accidentally but it just takes some more time to edit. Anyway I don't complaint much about this data editing in Data tab/view for tables but I am going to miss this feature in Query tab as I can't edit my data resultset grid.

Conclusion:
Looking forward to see better HeidiSQL with Final Release of 4.0 as it seems to be they are working hard to get it right. As we can see nightly build for every day on the download section but RC1 has been out for sometime now.Similar Posts:

• HeidiSQL 5.1 – good has got better
• backup/restore MySQL db using MYSQLDUMP (quick reference)
• Top free / open-source tools for MySQL Development / Administration
• MySQL5 Problem while creating new user – SQL Error (1133): Can’t find any matching row in the user table
• MySQL 5.5.8 – Problem while Creating new User (SQL Error (1364): Field ‘authentication_string’ doesn’t have a default value)

MySQL 5.1 general availability is announced and it is available to be used for production use.

MySQL 5.1 brings many new enhancements in the bag for world's most popular open source database. which includes Partitioning, Row based Replication, new Plugin Infrastructure and there are many more including general enhancements.

There is a long list of new enhancements which you can go through in What's New section here.

Download it here if you are ready to put it in production or want to play with it in your development enviornment.Similar Posts:

• MySQL 5.5 available for production
• Setting up PHP, MySQL, Apache with most up-to-date WAMP Package
• backup/restore MySQL db using MYSQLDUMP (quick reference)
• Alternate to FIND_IN_SET for non-MySQL databases
• HeidiSQL 4.0 RC1 released

1. phpMyAdmin

phpMyAdmin is a tool written in PHP intended to handle the administration of MySQL over the Web. Currently it can create and drop databases, create/drop/alter tables, delete/edit/add fields, execute any SQL statement, manage keys on fields.

Most basic and must have tool and everyone is aware of it associated with PHP/MySQL and your shared web host must be providing you this tool to manage your databases on the web.

Type: Web based/OpenSource
URL: http://www.phpmyadmin.net

2. HeidiSQL

HeidiSQL is an easy-to-use interface and a "working-horse" for web-developers using the popular MySQL-Database. It allows you to manage and browse your databases and tables from an intuitive Windows® interface. With HeidiSQL you will also be able to

• generate nice SQL-exports
• synchronize tables between two databases
• manage user-privileges
• import text-files
• export table-data as CSV, HTML and XML
• browse and edit table-data using a comfortable grid
• batch-insert ascii or binary files into tables
• write queries with syntax-highlighting (next version will have also code-completion)
• monitor and kill client-processes
• connect to servers via commandline
• and much more

HeidiSQL is the best desktop based MySQL Administration tool I have ever used and I am in love with it since I have started using it. In my opinion it even beats many top selling commercial MySQL GUIs too.

Type: Desktop/Opensource
URL: http://www.heidisql.comScreenshots: http://www.heidisql.com/screenshots.php
Download: http://www.heidisql.com

3. MySQL GUI Tools

MySQL management tools from the MySQL itself, they are holding lot of potential and one of the must have with kind of tools.

MySQL GUI Tools include
- MySQL Administrator
- MySQL Query Browser
- MySQL Migration Toolkit
Available for Windows/Mac/Linux platform.
Type: Desktop/ (GPL / commercial) Dual licensing.
URL: http://dev.mysql.com/downloads/gui-tools/

4. MyDB Studio

MyDB Studio is a complete collection of powerful tools for MySQL Server administration.

Major features are listed below from their website.

• SSH tunneling to secure your connections which allows you to connect even your host doesn't allow you remote access connection.
• Admin privileges users with User Manager
• Reload Server
• Flush internal caches of MySQL uses
• View/Kill server process
• Export Server Variables in XML, Excel, Word, CSV
• Create/Modify/Delete Database
• Backup/Restore database
• Export Database Table info in XML, Excel, Word
• Synchronise your database
• Create complete Php scripts
• Search in MySQL manual with MyDB Studio Embed Browser

URL: http://www.mydb-studio.com
Screenshots: http://www.mydb-studio.com/index.php?lang=en&p=2
Download: http://www.mydb-studio.com/index.php?lang=en&p=3

5. SQL Front

SQL-Front is a graphical GUI for the MySQL database. SQL-Front presents a uniform front-end for all of your current database projects. In practice, you can work with the database of your choice after only a few clicks.
It helps to:

• Define and manage the database-structure, import data, editing data is now simple with this full-featured program. For designers with only a basic grasp of databases, this program is the way to go to make you independent of SQL gurus.
• SQL-Front makes working with MySQL databases a snap without hiding the language from the user. The built-in SQL Editor provides syntax highlighting and context sensitive help, so even working with SQL commands and scripts will be a matter of convenience.

URL: http://www.sql-front.com
Screenshots: http://www.sql-front.com/screenshots.html
Download: http://www.sql-front.com/download.html

6. SQLyog MySQL GUI - Community Edition

One moe good GUI tool for MySQL. SQLyog comes with Enterprise license mode too with some more ability. Other commercial products from SQLyog includes

• SQLyog MySQL GUI - Enterprise Edition
• MONyog MySQL Monitor and Advisor

From both above later MONyog Monitor and Advisor has more attracted me as it provides nice statics and chart and tips/advises for optimizing MySQL performance. Actually it is worth having licensed administration tool for DBAs.

URL: http://www.webyog.comSimilar Posts:

• HeidiSQL 5.1 – good has got better
• backup/restore MySQL db using MYSQLDUMP (quick reference)
• MySQL5 Problem while creating new user – SQL Error (1133): Can’t find any matching row in the user table
• MySQL 5.5.8 – Problem while Creating new User (SQL Error (1364): Field ‘authentication_string’ doesn’t have a default value)
• HeidiSQL 4.0 RC1 released