- This topic has 6 replies, 2 voices, and was last updated 8 years, 10 months ago by
kiwi.
Tags: Export/Import kiwitrees 2.0.2
-
27th July 2014 at 4:42 am #3297
Nigel:
I exported a test installation tree GEDCOM file and then attempted to import it back in without any edits to the file. Keep getting the following error “SQLSTATE[22003]: Numeric value out of range: 1264 Out of range value for column ‘d_julianday1’ at row 1”. I cannot find anything wrong with the dates in the file. It is the first time I tried this since kiwitrees Ver. 2.0.2
Any ideas?
Thanks?
Roy
Roy
Roy
Apache 2.4.27 PHP 7.19 MariaDB 10.2.8
-
27th July 2014 at 7:40 am #3298
Can you send me the GEDCOM file?
Nigel
My personal kiwitrees site is www.our-families.info -
27th July 2014 at 8:08 am #3299
Nigel:
Will email it tomorrow morning, will be away the rest of the evening.
Thanks.
Roy
Apache 2.4.27 PHP 7.19 MariaDB 10.2.8
-
28th July 2014 at 8:46 am #3300
Roy, bad news I’m afraid. It imported perfectly on both my development system, and the demo system here at kiwitrees.net. I tried both as the demo is virtually standard kiwitrees.2.0.2, whereas my development system has had many changes since then, though I can’t recall any that would have any link to the error you are seeing.
Just in case it is something in the way your server is configured I have reviewed all the dates to see if there are any that might cause problems. There are a couple that are wrong so you could try another import after correcting these. The following have lines numbers from a simple text view of the GEDCOM file you sent me:
77295 2 DATE 1884 MAR
241441 2 DATE /25/1884
110682 2 DATE 16 APR
171585 2 DATE 17 FB 1962
77295 2 DATE 1884 MAR
104389 2 DATE 19 MAR
184738 2 DATE 19 MAR
127943 2 DATE 20 OCT
101719 2 DATE 25 SEP
110688 2 DATE 29 MAY
258558 2 DATE 30 AUG
184957 2 DATE AB T 1970
75077 2 DATE AF 04 MAR 1909
71770 2 DATE ANT 1923
118227 2 DATE AUGThe ones with no year are possibly the most contentious. (like 2 DATE 20 OCT) They are probably not the cause of the error, but will make life hard for the code in many places. Basically I recommend that a date is not a date without a year. If you only know the day/month, include it as a note until the year is identified.
Nigel
My personal kiwitrees site is www.our-families.info -
28th July 2014 at 9:46 pm #3301
Nigel:
Thanks for going “way beyond” with your assistance.
Correcting the dates didn’t do the trick. There must be an issue in the MySQL database. I will be rebuilding the test site when I have some free time. Thank goodness it didn’t happen on my live site.
Thanks again for all your help.
Roy
Apache 2.4.27 PHP 7.19 MariaDB 10.2.8
-
28th July 2014 at 9:58 pm #3302
I’ve not got access right now, but tell me what the structure of your wt_dates table is and I’ll compare it with mine. That is the table your error report is pointing to, and suggests an unusual limit on the size of the d_julianday1 column.
Nigel
My personal kiwitrees site is www.our-families.info -
28th July 2014 at 9:58 pm #3303
I’ve not got access right now, but tell me what the structure of your wt_dates table is and I’ll compare it with mine. That is the table your error report is pointing to, and suggests an unusual limit on the size of the d_julianday1 column.
Nigel
My personal kiwitrees site is www.our-families.info
- The topic ‘SQL error on export/import’ is closed to new replies.