Page 1 of 1

Bug in SQL-Export

Posted: 2005-11-12 01:45:07
by bcn
Hi,

I usually export my movies in a sql-database.
In earlier versions the sql-export worked like a charm, but
since the last two or three versions the option "sql-date-format" for exports does not work anymore. Regardless what is in this field (for example yyyy'-'mm'-'dd), dates are always exported in windows-format (11.11.2005) and this makes mysql get some crazy dates ...

Can you please check this and fix it.

Thanx alot.

greetings from germany
bcn

Posted: 2005-11-12 10:09:00
by antp
You have version 3.5.0.2 ? For me it seems to work fine.

Posted: 2005-11-12 22:11:06
by bcn
Yes, I have Version 3.5.0.2 from 2005.05.29. I installed your latest Package from 2005.10.15.

If I remember correctly, the Problems came with the first version of 3.5.02 from 2005.05.29.

I tried many variations of format in the "sql-date-format", with " as a separator as well as ' - nothing helps - The Date export is always in the standard Windows form (12.11.2005 with my windows).

I also tried a new, empty Catalog and created only one entry, with the same results.

I have Windows XP Pro german, SP2 with all Fixes installed.


I just made some further experiments:
- I changed the date format in Windows to "2005-11-12" with the effect that I get an empty date-field in the sql-export.
- I changed the "sql-date-format" field to "", the same effect - empty date-field in export
- I changed back to my Windows-Date-format and the "sql-date-format" field to 2005'-'11'-'12, with the same effect that the date-field in sql is empty .... now thats strange - before I changed settings, the sql-date was in windows-format with exact these settings ...

I hope you can help me ... please

thanx
bcn

Posted: 2005-11-13 10:21:52
by antp
You type 2005'-'11'-'12 in the field? I guess that you mean yyyy'-'mm'-'dd like in you first post.
On my Windows the date format is yyyy-mm-dd and if I put for example dd'/'mm'/'yyyy in the preferences, the "added date" field in sql export follow this format.

Posted: 2005-11-13 12:18:22
by bcn
of course i typed yyyy'-'mm'-'dd in the field - sorry for this ...

can it be that it has something to do with the reading/writing of xml-files?
Is it possible that I have installed something that changes the behavior of reading or writing of xml-files? But I save the Movie-Catalog in XML-Format also and this seems to be ok.
I browsed through the prefs.xml file and notived that under "export" the SQLDate Entry was always empty even if i used some of the predefined entries in the options-window.
I then changed the entry manually to SQLDate="yyyy'-'mm'-'dd", and when I rechecked the prefs.xml file the entry changed to the following:

<Export LoadTemplate="-1" LineBreak="<br>" ForcePicSizeW="-1" ForcePicSizeH="-1" SQLDate="yyyy'-'mm'-'dd" RememberLastFile="-1" LastFile="BCN_Movies.sql" OpenExportedFile="0" ExpFileStyle="0" ExpFileExt="" AddZeroes="-1" CopyPictures="-1" CopyPicturesNew="-1"/>

Is this correct?

The SQL-Export now has a date in the field, but like before in the Windows-FOrmat dd.mm.yyyy ...

I will now try the program in another windows and see what I get there ...

Posted: 2005-11-13 13:51:14
by antp
The program has its own XML engine so I do not think that the problem could come from there... It is really strange :/

Posted: 2005-11-16 13:57:36
by bcn
I found the problem!

I installed the program on another pc and tried the export with your demo-database and the date-format was correct.
Then I opened my database and exported it to sql - date-format correct also.
Next I copied the prefs.xml from the newly installed version to the program dir. of my pc - and it works!
The Date-Format is correct now, the disadvantage is that I have to redo all the configuration-settings.

So there must be an error in the prefs.xml file - I looked at it and compared it with the "empty" prefs-xml file - I could not figure out an obvious error ...

If you are interested I can mail you the defect prefs.xml file.

greetings from germany
bcn

Posted: 2005-11-16 16:01:50
by antp
Yes it could be interesting to prevent the bug in the future ;)