Corrupted data after import from LM
2 posts by 2 authors in: Forums > CMS Builder
Last Post: March 6, 2012 (RSS)
By mbodamer - March 5, 2012
Hi,
We had you guys do an import of data as we migrated from LM to CMSB. At first glance the data looked like it was there however there were thousands of listings. We are in the final stages of getting the new system fully operational and almost ready to switch over however we found a bunch of listings that the data did not import fully. It's hard to put a finger on it, but it seems like listings that had single or double quotes in the listing data then the import stopped at the quote and skipped the rest.
Anyone else run into this, would this be the cause of the failed import?
I am not replying to my support ticket becuase that was months ago that the import was done so I guess it would be considered a different case.
Thanks for any advice.
We had you guys do an import of data as we migrated from LM to CMSB. At first glance the data looked like it was there however there were thousands of listings. We are in the final stages of getting the new system fully operational and almost ready to switch over however we found a bunch of listings that the data did not import fully. It's hard to put a finger on it, but it seems like listings that had single or double quotes in the listing data then the import stopped at the quote and skipped the rest.
Anyone else run into this, would this be the cause of the failed import?
I am not replying to my support ticket becuase that was months ago that the import was done so I guess it would be considered a different case.
Thanks for any advice.
Re: [mbodamer] Corrupted data after import from LM
By Dave - March 6, 2012
Hi mbodamer,
I've seen that before, I think it was when the data had some chars (UTF-8) that weren't correctly encoded and not accepted by MySQL causing all following data to be ignored.
Probably the easiest thing to do would be to reply to start by replying to the old ticket so we can sort out what happened and get it fixed up for you. If you don't get a response within a couple days start a new ticket or post back here.
Hope that helps!
I've seen that before, I think it was when the data had some chars (UTF-8) that weren't correctly encoded and not accepted by MySQL causing all following data to be ignored.
Probably the easiest thing to do would be to reply to start by replying to the old ticket so we can sort out what happened and get it fixed up for you. If you don't get a response within a couple days start a new ticket or post back here.
Hope that helps!
Dave Edis - Senior Developer
interactivetools.com
interactivetools.com