- .SQL exported data is not 100% compatible with phpMyAdmin. MySQL-Front exports ## comments, while hpMyAdmin expects -- comments,
so you will get warnings, when trying to import MySQL-Front exported data into phpMyAdmin.
- When exporting to .SQL format, latin characters (accented i,e,o,u) in my database were converted to question marks ?.
This shouldn't happen. I think this is a bug.
Pros: Easy to use.
Cons: Not a offline Database editor. You can't import .sql file, edit the database, and then export .sql file, in an offline mode.
Sam, mysql isn't a "offline" database. you could download the MySQL independent ZIP archive and use it as the database or a portable all-in-one version like xamp or wamp.
I use Nils (R.I.P. mny friend) mysql-front for about 15 years and still love it!
Having used other front-end programmes, this is the easiest I've come across.
Definitely recommend it to any level of expertise as it's so easy to navigate and setup for local or remote access.
- .SQL exported data is not 100% compatible with phpMyAdmin. MySQL-Front exports ## comments, while hpMyAdmin expects -- comments,
so you will get warnings, when trying to import MySQL-Front exported data into phpMyAdmin.
- When exporting to .SQL format, latin characters (accented i,e,o,u) in my database were converted to question marks ?.
This shouldn't happen. I think this is a bug.
Pros: Easy to use.
Cons: Not a offline Database editor. You can't import .sql file, edit the database, and then export .sql file, in an offline mode.
I use Nils (R.I.P. mny friend) mysql-front for about 15 years and still love it!
Definitely recommend it to any level of expertise as it's so easy to navigate and setup for local or remote access.