MySQL 8.0 has been released as stable (GA) earlier this month. For db4free.net this means it’s time to make MySQL 8.0 the default version and to deprecate the MySQL 5.7 server instance.
The new MySQL 8.0 server is running on the default port 3306. All new registrations will have the database created on this server. It is fresh and empty and will start from scratch.
The previous MySQL 5.7 server will remain available on port 3308. All users who have data there which they want to keep should migrate it to the new MySQL 8.0 server. This will require you to sign up again.
The previous MySQL 8.0 server will remain on port 3307. Both the old MySQL 5.7 and the old MySQL 8.0 server on port 3307 will be available until June 15, 2018. Data which isn’t migrated to the new server instance by then will be lost.
The new MySQL 8.0 server instance will come with the new utf8mb4 character set and the new utf8mb4_0900_ai_ci collation, which are the new defaults in MySQL 8.0. Since db4free.net already used utf8mb4 on the previous MySQL 5.7 server instance, this should not affect many people, if any at all.
Another long overdue change is that the default timezone (on db4free.net, this is not a change in MySQL 8.0 itself) will be UTC. Previously the servers were set to Central European Time since that’s the home time zone where db4free.net is hosted. But with a large international audience it makes sense to use UTC going forward. The timezone can be changed per connection as described in the MySQL Reference Manual.
The MySQL 8.0 Reference Manual is the place to go for all general MySQL questions and to find out what’s new in MySQL 8.0 (which are a lot of things).
As always: please backup data which you can’t afford to lose. db4free.net is a testing service and there is always a risk that something goes wrong, like the server doesn’t start up anymore. This has happened before and may happen again, especially with a brand new version. This service comes with no warranties at all.
If you keep that in mind you should have much fun exploring the new (and old) goodies of MySQL 8.0. Consider following db4free.net on Twitter as this is where you get updates and status information the quickest.
20 thoughts on “db4free.net goes MySQL 8.0”
Two weeks ago I was trying to connect to my db4free.net data base from my java aplication (with JDBC connector and the url conetion “jdbc:mysql://db4free.net:3306/my_db”) and I could do it. The last 28th of april you maked changes in the db4free.net server and since that date I can´t connect from my java aplication. My java aplication return an error like this “Communications link failure/The last packet successfully received from the server was 484 milliseconds ago. The last packet sent successfully to the server was 453 milliseconds ago”.
Can you help me, please!!!!
Thak you so much!!!
Is there any chance to save the data from the old server? I have used it as a demo database and now everything is gone..
No, the data on the old servers have been completely deleted, as noted in this article:
“The previous MySQL 8.0 server will remain on port 3307. Both the old MySQL 5.7 and the old MySQL 8.0 server on port 3307 will be available until June 15, 2018. Data which isn’t migrated to the new server instance by then will be lost.”
Thank you for the service but why I’m not able to create trigger?
Trigger privileges should be granted to your account and your database.
If you run SHOW GRANTS you should see a line GRANT ALL PRIVILEGES ON `your_database`.* TO `your_user`@`%`.
Hi. I was trying to connect to my db4free.net data base from but i can’t and i don’t know why
Are you still unable to connect? Do you get any messages?
Not able to login into my account ,
What is the problem?
There is now a new server, starting from scratch. The old server is available on port 3307, probably you can access your account there. phpMyAdmin has a dropdown where you can access this deprecated server.
If you need your data you should migrate it to the new server ASAP. The deprecated server will be removed in a few weeks.
Thank you for db4free net. I
t’s helping me a lot in testing apps before actually buying hosting.
I am sure there are many who has benefited from this service.
Once again, Thank you! Have a great day!
what is hostname?
Hostname is db4free.net
Dear Mr Popp
Thanks for this great service. I enjoy to use it with my students. Do you know how to speed up the data retrieval using SQL and PHP from my personal Webserver? Sometimes a query takes up to 30secs. Am I doing something “wrong”? Thank you very much.
Dear Mr. Propst,
if queries are only *sometimes* slow, it’s likely due to the load of the server at that particular moment. If queries are always slow, it’s more likely they need optimization.
The MySQL Reference Manual provides a few chapters which may be interesting for you, like:
Optimizing SQL Statements:
Optimization and Indexes:
Understanding the Query Execution Plan:
I hope this helps.
Connectors should work with any MySQL database, so with db4free.net too.
#1055 – Expression #2 of SELECT list is not in GROUP BY clause and contains nonaggregated column ‘db_capev.C.CARACT’ which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_group_by
it is necessary to deactivate in this version only-full-group-by
set global sql_mode=’STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION’;
Via windows command line I had the follwing error message:
C:\Users\Ronney>mysql -h db4free.net -u ronney -p
Enter password: *************
ERROR 1045 (28000): Access denied for user ‘ronney’@’184.108.40.206’ (using password: YES)
Can someone help me please.
This may have been a temporary outage (like for maintenance).
I had tried since yesterday using vfp 9 to connect and create table also insert the data successfully, but the problem I can’t retrieve the data from table just created. I don’t find any problem running the same code in my local installed wamp using mysql 5.7. Error in line :
=SQLEXEC(ConnHandle, “select * from sdata” , “mycursor”)
Is a problem with mysql 8 not supporting query using select in vfp 9?