Hi Gabi,

Thanks for reporting the issue.  To make it easy for us to help you as quickly as possible could you please provide the following?
  i) the actual log lines from the IPT logs
  ii) the SQL statement you are using
  iii) a small sample table so we can recreate the issue

This is a wild guess, but I suspect tat dateTime formats is not being handled gracefully.  If possible can you please try timestamp SQL column format instead of dateTime to see if that narrows down the cause? (I understand this is not a viable fix, but might help identify the root of the issue)

Thanks,
Tim

On Oct 17, 2013, at 2:44 PM, Dröge, Gabriele wrote:

Dear all,
 
I’ve downloaded the latest IPT version 2.0.5-r4398 and tried to map my data.
I want to use a MySQL database, but there seems to be a bug in IPT concerning MySQL.
IPT is not able to handle the SQL statement even though it is correct (tested on the MySQL server directly)
Log file says:
1.       Error in SQL (there is definitely no error in the sql statement)
2.       IPT expects one more column than the sql statement queries for (unclear why)
3.       IPT can’t handle datetime (unclear why)
 
A CSV file and a connection to a MS SQL Server did work.
 
Preview looks like this:
 
<image001.jpg>
 
 
It would be great if someone could fix those bugs.
Thanks in advance!
 
Best wishes,
Gabi
 
-----------------------------------------------------------------
Gabriele Droege
Coordinator - DNA Bank Network
Global Genome Biodiversity Network (GGBN)
Berlin-Dahlem DNA Bank
Deputy Women's Officer ZE BGBM
 
Botanic Garden and Botanical Museum Berlin-Dahlem
Freie Universität Berlin
Koenigin-Luise-Str. 6-8
14195 Berlin
Germany
 
+49 30 838 50 139
 
_______________________________________________
IPT mailing list
IPT@lists.gbif.org
http://lists.gbif.org/mailman/listinfo/ipt