All I want for Christmas is...
HeidiSQL 3.0 final :lol:
Keep up the good work HeidiSQL team.
Why I like HeidiSQl:
1. Its power to weight ratio is amazing. (for less than 2MB its punching above its weight)
2. GUI is simple & intuitive
3. Its stable & fast
4. Where point 3 doesn't hold, its quick and easy to kill.
5. Point 3 is improving constantly.
6. Its free.
HeidiSQL brings a smile to my face every time I open it up .. like this :D
All I want for Christmas is...
Hallo,
Nutze schon seit ein paar Jahren MySQL-Front.
Mit dem upgrade auf 4.1 MySQL bei meinem Provider begannen die Probleme.
Habe dann aber Heidi gefunden!
Was mir noch fehlt, ist ein Konverter von access --> MySQL, also der
ODBC-Import vom MySQL-Front.
Habe mir gerade den Intelligent Converter von convert-in.com gekauft.
Leider interpretiert er die ja/nein Felder nicht als ENUM ('True','False') sondern als TINYINT(4) und alle Datenbankabfragen funktionieren nicht mehr! :cry:
Nutze schon seit ein paar Jahren MySQL-Front.
Mit dem upgrade auf 4.1 MySQL bei meinem Provider begannen die Probleme.
Habe dann aber Heidi gefunden!
Was mir noch fehlt, ist ein Konverter von access --> MySQL, also der
ODBC-Import vom MySQL-Front.
Habe mir gerade den Intelligent Converter von convert-in.com gekauft.
Leider interpretiert er die ja/nein Felder nicht als ENUM ('True','False') sondern als TINYINT(4) und alle Datenbankabfragen funktionieren nicht mehr! :cry:
The ODBC-import tool from MySQL-Front 2.5 has been completely nuked as there were too many bugs in it, and we had several problems with dataloss and identification of datatypes. The import-tool has not been rewritten yet for the RC4.
But I can give away some other secrets which will be in RC4:
- a SQL-Help window which is context-sensual on keywords written in the Query-tab
- completion-proposal in the Query-tab, including SQL keywords, functions, tablenames and columnnames
- a new list containing command-statistics
- a simple snippet-management.
these 4 new things are only a small fragment of a huge changelog... :D
But I can give away some other secrets which will be in RC4:
- a SQL-Help window which is context-sensual on keywords written in the Query-tab
- completion-proposal in the Query-tab, including SQL keywords, functions, tablenames and columnnames
- a new list containing command-statistics
- a simple snippet-management.
these 4 new things are only a small fragment of a huge changelog... :D
Is there any way to make a connection by MySQL-Front with MySQL 4.1, only for ODBC Import? I never had problems with bugs by ODBC-Import.
When I start MySQL-Front, I get information, that I must make update. :?
The only small bug with Heidi, wich I have, is, that she is standing on end, when she is ready, and does
When I start MySQL-Front, I get information, that I must make update. :?
The only small bug with Heidi, wich I have, is, that she is standing on end, when she is ready, and does
In MySQL-Front 2.5 there was a menu-item in Import/Export called ODBC-Import. Click on it and you will be asked for a source-database (ODBC-DSN or MS-Access file). Then MySQL-Front 2.5 will try to detect all column-types, defaults and other properties. The latter thing is kind of buggy if I rememeber correctly. But you should try it. :)
In deed, it was.
But my problem is the connect with MySQL-Front to MySQL 4.1
After Update by my provider, I skip the 3. MySQL maschine an also upgrade at 4.1
Now I get no connection when I start MySQL-Front. The answer is:
"Connection failed.
1251 - Client does not support authentification protocol requested by server; consider upgrading MySQL client."
and without connection I can`t use ODBC import.
But my problem is the connect with MySQL-Front to MySQL 4.1
After Update by my provider, I skip the 3. MySQL maschine an also upgrade at 4.1
Now I get no connection when I start MySQL-Front. The answer is:
"Connection failed.
1251 - Client does not support authentification protocol requested by server; consider upgrading MySQL client."
and without connection I can`t use ODBC import.
from support convert-in.com I get the answer that it still convert MS Access true/false into MySQL 1/0 because it is the most proper conversion.
So I change the fields Yes / No in Access in text and with search/"ersetzen" No to False an Yes to True my problem is not more exist.
But Access-to-MySQL is verry slowly, what the ODBC Convert from MySQL-Front done in 30 sec., the new tool need over 5 min.
So I change the fields Yes / No in Access in text and with search/"ersetzen" No to False an Yes to True my problem is not more exist.
But Access-to-MySQL is verry slowly, what the ODBC Convert from MySQL-Front done in 30 sec., the new tool need over 5 min.
In deed, it was.
But my problem is the connect with MySQL-Front to MySQL 4.1
After Update by my provider, I skip the 3. MySQL maschine an also upgrade at 4.1
Now I get no connection when I start MySQL-Front. The answer is:
"Connection failed.
1251 - Client does not support authentification protocol requested by server; consider upgrading MySQL client."
and without connection I can`t use ODBC import.
Try to reset the password to "pre-4.1", see: http://dev.mysql.com/doc/refman/5.0/en/old-client.html
All I want for Christmas is...
HeidiSQL 3.0 final :lol:
Done: 3.0 final is out. Grab it from here: http://prdownloads.sourceforge.net/heidisql/HeidiSQL_3.0_Setup.exe?download
Really appreciate RC4 just before Christmas and now V3 Final
I've just downloaded this latest version, and the speed is starting to look more like MysqlFront2.5.
I love the fact that exporting to a different server is now working. It has already come in handy... showing it off to one of my colleagues.
I will be looking forward to exploring new features in the coming days.
Thanks again!
I've just downloaded this latest version, and the speed is starting to look more like MysqlFront2.5.
I love the fact that exporting to a different server is now working. It has already come in handy... showing it off to one of my colleagues.
I will be looking forward to exploring new features in the coming days.
Thanks again!
Please login to leave a reply, or register at first.