Support

Admin Tools

#20236 Bad database migration with AdminTools for j3 installed

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by carukc on Wednesday, 11 June 2014 11:16 CDT

carukc
 Hello,

This is just for your information... I have worked around the problem...

While trying to copy the my dev MySQL database from my workstation to a VM using Navicat I was unable to complete the migration due to a problem in the admintools tables.

MySQL reported:

[Err] [Dtf] 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 '
`created_on` datetime NOT NULL DEFAULT '0000-00-00 00:00:00' ,
`created_by` ' at line 10
[Err] [Dtf] Finished - Unsuccessfully

during the migration.

I have replicated by completely uninstalling AdminTools. deleting all adminTools tables, reinstalling AdmiTools and then migrating. So the problem occurs during the install of AdminTools.

I've worked around by uninstall admintools, migrating and then reinstalling on the VM.

So... just FYI.

Chris

nicholas
Akeeba Staff
Manager
The syntax we use for creating the database tables is valid, but the syntax generated by Navicat when it was dumping our tables was invalid and NOT what we are using in our own code. This is a Navicat bug.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

carukc
Good to know. Thanks.

Strangely. I also migrated several sites on v2.5 and they worked fine so there must be a difference between the way data is stored on j2.5 and j3.

nicholas
Akeeba Staff
Manager
There's absolutely no difference. You are installing the same package which runs the same SQL queries on installation on both J! 2.5 and 3.x.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

carukc
Very strange. It worked perfectly on all the j2.5 databases and only threw the error on the j3.3 database. I'll check to see if the v2.5 and v3 databases are both UTF8. That may have something to do with it but I suspect that you are right that it's a problem with Navicat. I had only sent the note to you because the problem only occurred on one DB and the only thing different about that db was that it contain a j3.3 install... I though that if you were doing something different on j3.3 you might want to know that there might have been a problem.

Thanks again for your response and keep up the great work on Akeeba and Admin tools. I would not want to deploy a joomla site without them!

Kind Regards
Chris

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!