Posts

SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column ‘s_name’ at row 1

Any tips on how to find the culprit would be _much_ appreciated! It’s a large ged.

The ged also has \x92,93,94 and 96 – fixed those with HxD. Was/is there a way to change encoding to allow extended character set?

Cheers

Chronplex GEDCOM Validator.. to the rescue.

Sorry for the delayed response – busy weekend.

phred wrote:

SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column ‘s_name’ at row 1

‘s_name’ is “Source name”. Limited to 255 characters.

phred wrote:

Any tips on how to find the culprit would be _much_ appreciated! It’s a large ged.

The ged also has \x92,93,94 and 96 – fixed those with HxD. Was/is there a way to change encoding to allow extended character set?

These are UTF-8 encoded strings. Thats normal, so shouldn’t be a problem.
But check your GEDCOM file. Near the start shoulld be a line like

1 CHAR UTF-8

If it says anything other than UTF-8, and you have no other reason for a different character set, just change it and re-import.

Nigel
My personal kiwitrees site is www.our-families.info

Hi Nigel,

Thanks for the reply. I’m fighting to get trees off A.com – unfortunately spent considerable effort over the last 15+ years building several  thoroughly researched, sourced and documented (with media) trees online at A.com. Modest in number of individuals (largest 530) but lots of media attached (including census images) and source citations.

Fortunately I had saved all uploaded media, unfortunately not census images, and of course A.com ged export doesn’t attach census images. I do have RootsMagic and have used it to get the trees including census images. Bad news is RootsMagic export .ged is a mess.

At the moment current plan is to write a RootsMagic .ged fixer program. I’m just now looking at how much damage the Roots <- A.com import did to base data and then how to fix the Roots .ged.

Please wish me luck!

Cheers,
Phred

P.S. I see my first post was back in 2013 – should have gone with Kiwitrees back then..

You have my sympathy, though A.com is not the worst. That honour, in my experience, goes to MyHeritage.

Once you get to the stage of importing, in whatever state, a GEDCOM into kiwitrees these are the tools available internally that might help (in case you are not fully aware of them)…

1. Administration > Family tree tools > Check for GEDCOM errors
2. Administration > Family tree tools > Sanity check
3. Administration > Tools > Batch update > Search & replace

Nigel
My personal kiwitrees site is www.our-families.info