MySQL Forums
Forum List  »  PHP

Error import : #1064 - You have an error in your SQL syntax;
Posted by: david ronchaud
Date: November 17, 2015 11:52AM

Hello everyone,

First of all, please excuse me for my bad english. So, I'm David and I've a problem since some days... Let me explain this problem.

I've UwAmp and I develop a Prestashop in local environment. Then, I try to upload my prestashop to my server (a VPS Cloud from OVH). So I export my database from my UwAmp PhpMyAdmin and after, I try to upload to my Server PhpMyAdmin but I've the following error :
__________

#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 'CREATE TABLE `ps_ye_mail` (
`id_mail` int(11) unsigned NOT NULL,
`recipient` v' at line 98
__________

This error block the importation and there are only 132 first table on 250 total...




If I separate my export in two parts (one from the begin to the n°132, before ps_ye_mail, and the second from the ps_ye_mail to the end) my import has no error. BUT my e-shop has the following error if I try to access to my cart page :
__________
[PrestaShopDatabaseException]

Subquery returns more than 1 row

UPDATE `ps_ye_cart_product`
SET `id_address_delivery` = (
SELECT `id_address_delivery` FROM `ps_ye_cart`
WHERE `id_cart` = 0 AND `id_shop` = 1
)
WHERE `id_cart` = 0
__________


Look at the code from PhpMyAdmin export of the corresponding table :

CREATE TABLE `ps_ye_mail` (
`id_mail` int(11) unsigned NOT NULL,
`recipient` varchar(126) NOT NULL,
`template` varchar(62) NOT NULL,
`subject` varchar(254) NOT NULL,
`id_lang` int(11) unsigned NOT NULL,
`date_add` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP
) ENGINE=InnoDB DEFAULT CHARSET=utf8 AUTO_INCREMENT=1 ;



Have you an idea for help me to resolve this problem ?

I hope that I was quite understandable... If is not, let me know.
I'm looking forward to looking from you and I thank you for your help!
David!

Options: ReplyQuote




Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.