Illegal double when importing db using wootickets

[Bruce Scher]

I am having a really hard time importing data form a customer site so i can do update on it for them.

Does anybody no why I would be getting the following

INSERT INTO fl_postmeta (
    meta_id,
    post_id,
    meta_key,
    meta_value
) VALUES ( 
    165326, 
    3283, 
    '_tribe_wooticket_security_code', 
    '7482a6e822'
);

MySQL said: Documentation
1367 - Illegal double '342e880385' value found during parsing

My Question is why would this be the case when i exported from a linux platform to xamp for testing how do i fix this
I am importing form a linux host to a xamp environment for testing didnt think their should be a problem

• This topic was modified 10 years, 3 months ago by Bruce Scher.
• This topic was modified 10 years, 3 months ago by Bruce Scher.
• This topic was modified 10 years, 3 months ago by Bruce Scher.
• This topic was modified 10 years, 3 months ago by Bruce Scher.
• This topic was modified 10 years, 3 months ago by Barry.
• This topic was modified 10 years, 3 months ago by Barry.
• This topic was modified 10 years, 3 months ago by Barry.

[Barry]

Hi bruciebruce,

Thanks for posting!

The code you shared was slightly mangled – though I did my best to clean it up – so it may not perfectly match what you originally posted. Please note in future it’s usually best to share code by linking to Gist, Pastebin or some similar service 🙂

So for some reason MySQL is taking the string 342e880385 and is viewing it as a double precision number (probably because of the lowercase e in the middle).

Without knowing what the target schema looks like I’m not quite sure why that would be; but perhaps it is a quoting issue and you need to revise your insert statement/make use of properly prepared statements?

Have you written a custom script to perform this task or are you using standard tools like mysql / mysqldump on the command line?

Unfortunately, for a task like this, we’re probably not going to be able to provide too much assistance as its really a SQL/migration issue rather than a functional or operational issue with our plugin.

[Support Droid]

This topic has not been active for quite some time and will now be closed.

If you still need assistance please simply open a new topic (linking to this one if necessary)
and one of the team will be only too happy to help.

[Author]

Posts