Yes, as Gwyn mentioned, it is the trigger.

Thank you.



Gwyn wrote:
> 
> On Thursday, June 28, 2007, 7:46:22 AM, sepgs2004
> <[EMAIL PROTECTED]> wrote:
> 
>> EXCEPTION
> 
>> --- Cause: java.sql.SQLException: [Microsoft][SQLServer 2000 Driver for
>> JDBC][SQLServer]Syntax error converting datetime from character string.
> ...
> 
>> If we look at teh query in my L.xml
> 
>> <delete id="deleteLicenseByLicenseId"
>> parameterClass="java.lang.Integer">
>> <![CDATA[
>>                         DELETE FROM
>>                                 space.table_license
>>                         WHERE
>>                                 license_id = #value#
> ]]>>
>> </delete>
> 
> ...
> 
>> Could you guys give me some suggestions or thoughts.
> 
> My /guess/ would be a trigger or linked table or similar in the
> production DB causing an issue, if only because I can't think of
> anything else!
> 
> My approach would be to enable logging of the actual SQL being sent
> then try & reproduce it, first via a commandline tool then if that
> didn't show anything, using a Java test app & the same JDBC driver.
> 
> /Gwyn
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/This-is-really-weird...dateformat-mapping-exception-on-Integer-parameter-class-tf3992606.html#a11344208
Sent from the iBATIS - User - Java mailing list archive at Nabble.com.

Reply via email to