Front end for MySQL

Shandy

Junior Member
Joined
Apr 7, 2017
Messages
128
Reaction score
31
Hi, Total noob here when I comes to databases. I'm building a database in mysql hosted externally. I need a basic front end that will allow me to interact with it. I'm aware that Access allows this, is there any other simple tools that I should research though? Many thanks.
 
have a look through the google results "open source mysql database front end"
 
Hi, Total noob here when I comes to databases. I'm building a database in mysql hosted externally. I need a basic front end that will allow me to interact with it. I'm aware that Access allows this, is there any other simple tools that I should research though? Many thanks.

Access is easiest. You can also check out Yii, but it's annoying, and you will need PHP knowledge.

If you are a noob to databases, you should be extra careful. Go read about SQL Injection and how to avoid it. Use prepared statements if you're coding it yourself.
 
Access is easiest. You can also check out Yii, but it's annoying, and you will need PHP knowledge.

If you are a noob to databases, you should be extra careful. Go read about SQL Injection and how to avoid it. Use prepared statements if you're coding it yourself.
Thanks @bigot, good tip about injection.
 
Workbench is better if you don't have to administer it remotely. But if you gotta work with it remotely, then you should not keep mysql port open. Then you use phpmyadmin on the server.
 
Workbench is better if you don't have to administer it remotely. But if you gotta work with it remotely, then you should not keep mysql port open. Then you use phpmyadmin on the server.
Ahh! PHPMyAdmin is on the server (with the database) and Workbench is on the desktop, I had not really appreciated that.

When you say 'keeping the port open', do you mean having it constantly accessible through Workbench?
 
Depending on your host, they usually disable "remote" connections (connections not from localhost). You can turn this on in cPanel.

Try NaviCat. It's not free, but I like it a bit better than workbench.

phpMyAdmin is nice if you know what you're doing and write your queries by hand. Sounds like you like the drag-and-drop joins that Access has; new phpMyAdmin may have that... I vaguely remember seeing it, take this with a grain of salt.
 
Ahh! PHPMyAdmin is on the server (with the database) and Workbench is on the desktop, I had not really appreciated that.

When you say 'keeping the port open', do you mean having it constantly accessible through Workbench?

Exactly. If you leave the remote port open for workbench, then hackers can exploit it too.
 
Exactly. If you leave the remote port open for workbench, then hackers can exploit it too.
There's still authentication, they can't just get in by knowing the IP and port. Still worth being careful in case a new exploit is found; change the port if your host lets you, and use IP whitelist if your host has the feature since you will be using workbench from very few IPs.
 
So you need the frontend only for you or are you actually building a website/application that uses it? If the first one then you can use Access / HeidiSQL / Workbench / phpMyAdmin. But if you actually want to make software or website that uses the database, then you need to learn some backend coding like PHP/Java/Javascript(Node)/Ruby/Python and so on.
 
if you actually want to make software or website that uses the database, then you need to learn some backend coding like PHP/Java/Javascript(Node)/Ruby/Python and so on.

Except Access - You can make fairly complicated database forms/reports/etc. with no coding experience.
 
Except Access - You can make fairly complicated database forms/reports/etc. with no coding experience.

Depends how you want the database to be used. If you have a website with users coming in then you probably want to make it as easy to use as possible. I'm not even sure what methods do you mean but I wouldn't expect my users to use HeidiSQL or some other program to do CRUD actions in my website.
 
There's still authentication, they can't just get in by knowing the IP and port. Still worth being careful in case a new exploit is found; change the port if your host lets you, and use IP whitelist if your host has the feature since you will be using workbench from very few IPs.

There are tons of reasons to not leave mysql ports open. Try at your own risk.
 
Back
Top