Ads were blocked by your webbrowser.

This is not a problem, but keep in mind that developing HeidiSQL, user support and hosting takes time and money.

You may want to send a donation instead.

HeidiSQL 6.0 released

ansgar's profile image ansgar posted 9 years ago in Anouncements
This is a new release of HeidiSQL, the result of 331 changes done after the previous 5.1 release. HeidiSQL 6.0 introduces many new features of which I'll list the most important ones here:
- Tabs for multiple batch results or multiple procedure results in a query tab.
- Multiple connections in one application instance
- Editable query results
- Rewritten user manager, using GRANT and REVOKE syntax now
- Rewritten "Copy table" dialog and logic, supporting WHERE filters now
- Rewritten "Load text file" dialog and logic, supports client side parsing for situations where LOAD DATA is not allowed
- Rewritten SQL help dialog
- Query profiling in query tabs
- Introduce "Run current query" action (Shift+Ctrl+F9)
- Enhance detection of Unicode text files
- Server details hint when mouse over version status panel
- Internal image previewer for BLOBs
- LaTeX and Wiki markup output for grids
- ZEROFILL support in table editor
- Session manager: Prompt for username and password on demand
- Add support for TIME values above 24 hours
- Tons of bugfixes

Grab it
Dr. Dave's profile image Dr. Dave posted 9 years ago
Well... seems though you can't create any users.

Keep getting: SQL Error (1133):Can't find any matching row in the user table
ansgar's profile image ansgar posted 9 years ago
Looks like you activated SQL mode NO_AUTO_CREATE_USER, which does avoid to create users when you don't specify a password. Please type a password for new users in that case. The error message is though a bit misleading, but that's up to MySQL itself.

See
http://bugs.mysql.com/bug.php?id=7000
http://dev.mysql.com/doc/refman/5.0/en/server-sql-mode.html


Ads were blocked by your webbrowser.

This is not a problem, but keep in mind that developing HeidiSQL, user support and hosting takes time and money.

You may want to send a donation instead.
giuliano's profile image giuliano posted 9 years ago
Hi,
To avoid this problem, Heidi could launch the CREATE USER statement before launching the GRANT statement (when you create a new user).
Or Heidi could use "GRANT .. TO .... IDENTIFIED BY password".

I noticed HEIDI doesn't use the "IDENTIFIED BY" clause, but use two statement (GRANT and SET PASSWORD).

I think that if you'd use "GRANT ... IDENTIFIED BY...", the error wouldn't occur.
JonoB's profile image JonoB posted 9 years ago
When executing queries, the query tab used to show the number of records returned, and the execution time. Where do we get that information now?
ansgar's profile image ansgar posted 9 years ago
Please look into the lower log panel. This was moved in order to save space for the result grid when sub tabs were introduced.
ansgar's profile image ansgar posted 9 years ago
giuliano, you're right - that would at least solve that problem when a password was given. Will check that.
ansgar's profile image ansgar posted 9 years ago
CREATE USER implemented for 5.0.2+ servers in r3606. Old servers still use the SET PASSWORD query, which should never fail as NO_AUTO_CREATE_USER mode was added in MySQL 5.0.2, as was CREATE USER.
Dr. Dave's profile image Dr. Dave posted 9 years ago
Thanks, Anse. Creating new users works great now. smile
JonoB's profile image JonoB posted 9 years ago
Using -- to comment out lines in the query window causes an error.
Not closing /* with */ causes an error (*/ shouldnt be required if, for example, you are commenting the last line in the query)


Ads were blocked by your webbrowser.

This is not a problem, but keep in mind that developing HeidiSQL, user support and hosting takes time and money.

You may want to send a donation instead.
ansgar's profile image ansgar posted 9 years ago
"-- " syntax works here. Error message?

"/* " is not valid for MySQL. You must indeed include the closing stuff.
JonoB's profile image JonoB posted 9 years ago
SELECT a.id, a.name
--, a.code
FROM account a


#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ' a.code FROM account a' at line 2
ansgar's profile image ansgar posted 9 years ago
"--" comments need a space afterwards. See http://dev.mysql.com/doc/refman/5.1/en/comments.html .

Just the syntax highlighter is perhaps misleading as it displays the two dashes without space as comment, but that should be fixed in SynEdit.
JonoB's profile image JonoB posted 9 years ago
Thanks for clearing that up. I thought that the previous version worked without spaces, but no matter.
giuliano's profile image giuliano posted 9 years ago
The space after "--" is the "non-ANSI" part of MySQL SQL syntax for comments.
AFAIK, it was always required, and it doesn't depend on HeidiSQL but on MySQL.

mitislumen's profile image mitislumen posted 9 years ago
I just wanted to say, HeidiSQL is the best MySQL manager I have used. Nice work developers, version 6.0 works really well and is extremely useful and helpful for me, my life would be much much harder without it. Thanks you all for this.
admintiger's profile image admintiger posted 9 years ago
I agree. HeidiSQL is also the best MySQL manager I have used. I use it daily on several servers and greatly appreciate the work that is so generously contributed developing and continually improving it.
michaelgang's profile image michaelgang posted 9 years ago
great work !!! smile
acio83's profile image acio83 posted 9 years ago
Great app! but I'm missing theraded execution of queries. It's not cool to block the UI while executing a query. Also, a button to cancel the query would be nice.

Still I like it a lot and it's the app I use everyday, so thanks a lot!
nthdesign's profile image nthdesign posted 9 years ago
It looks like HeidiSQL is injecting a semicolon onto the end of every statement. For instance, consider the following statement:

DELIMITER $$


This statement now fails in HeidiSQL 6, when it worked fine in all previous versions of HeidiSQL. If you look in the statement log, you'll see that HeidiSQL is actually running the following statement:

DELIMITER $$;


Other than that, everything in HeidiSQL 6 has worked fine for me!

Thank you for putting so much effort into HeidiSQL. It is a tool I use every single day.
nthdesign's profile image nthdesign posted 9 years ago
I generally use the delimiter statement when creating stored procedures. For instance, I might execute the following SQL code:
DELIMITER $$
DROP PROCEDURE IF EXISTS spHelloWorld $$
CREATE PROCEDURE spHelloWorld()
BEGIN
SELECT 'Hello World!';    	
END $$
DELIMITER ;

As a follow-up, the workaround to this is to use the delimiter feature built into Heidi. If I click the delimiter button, and specify "$$" as my delimiter, then I can execute just the following:
DROP PROCEDURE IF EXISTS spHelloWorld $$
CREATE PROCEDURE spHelloWorld()
BEGIN
SELECT 'Hello World!';    	
END $$

Please login to leave a reply, or register at first.