Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Starting job Copy_of_BBdataTransform_2 at 15:16 15/05/2008.
Exception in component tMSSqlOutput_2
java.sql.SQLException: Line 1: Length or precision specification 0 is invalid.
at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:365)
at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2781)
at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2224)
at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:628)
at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:525)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:487)
at net.sourceforge.jtds.jdbc.JtdsStatement.executeImpl(JtdsStatement.java:664)
at net.sourceforge.jtds.jdbc.JtdsStatement.execute(JtdsStatement.java:1114)
at notifications.copy_of_bbdatatransform_2.Copy_of_BBdataTransform_2.tFileInputDelimited_2Process(Copy_of_BBdataTransform_2.java:910)
at notifications.copy_of_bbdatatransform_2.Copy_of_BBdataTransform_2.tFileList_1Process(Copy_of_BBdataTransform_2.java:360)
at notifications.copy_of_bbdatatransform_2.Copy_of_BBdataTransform_2.runJobInTOS(Copy_of_BBdataTransform_2.java:3530)
at notifications.copy_of_bbdatatransform_2.Copy_of_BBdataTransform_2.main(Copy_of_BBdataTransform_2.java:3429)
moment pid root_pid father_pid project job context priority type origin message code
2008-05-15 15:16:26|BfJQYR|BfJQYR|BfJQYR|NOTIFICATIONS|Copy_of_BBdataTransform_2|Default|6|Java Exception|tSendMail_6|Line 1: Length or precision specification 0 is invalid.|1
Job Copy_of_BBdataTransform_2 ended at 15:16 15/05/2008.
Currently it looks like when you press the "Guess" button and the field is null, the Type is set to String and the Length isn't given a value (or is given a null value, which translates to 0 to tMSSqlOutput - see quote below).
It would be nice if there was an option on the update/edit schema screen to set what you want the default Type and Length to be if a field comes up as null. (simple example of the kind of thing I mean : pic #3)
Or at least have the translation of the null value for Length set to something other than 0, so the error below doesn't happen.
Currently it looks like when you press the "Guess" button and the field is null, the Type is set to String and the Length isn't given a value (or is given a null value, which translates to 0 to tMSSqlOutput - see quote below).
It would be nice if there was an option on the update/edit schema screen to set what you want the default Type and Length to be if a field comes up as null. (simple example of the kind of thing I mean : pic #3)
Or at least have the translation of the null value for Length set to something other than 0, so the error below doesn't happen.