You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by "Robert S. Sfeir" <ro...@codepuccino.com> on 2005/06/04 15:09:13 UTC

SQL Conversion not working in 1.0.3???

Hey guys,

I've been trying to figure out if this is something OJB is doing or  
something Spring Framework's hooks are doing.

I have a definition of a field as follows:

          <field-descriptor
             name="submissionDate"
             column="ticket_submissionDate"
             jdbc-type="TIMESTAMP"
              
conversion="org.apache.ojb.broker.accesslayer.conversions.JavaDate2SqlTi 
mestampFieldConversion"
             >
         </field-descriptor>

The data incoming is a long and the Object is an instace of Date,  
which according to the converting class is correct.  After doing more  
stepping through the code in the debugger, I noticed that the  
conversion class never gets called.  I even set it to something  
completely ridiculous and nothing failed.

So the question is, did something fall off here in the move to ojb  
1.0.3 or is this something I should take up with Juergen on the  
Spring list?

Thanks
R

---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Re: SQL Conversion not working in 1.0.3???

Posted by "Robert S. Sfeir" <ro...@codepuccino.com>.
Nevermind.  Self brain fart, the repository xml I had modified was  
not deployed to the proper location for my unit test to find.

All is well, sorry for any inconvenience.

R

On Jun 4, 2005, at 9:18 AM, Robert S. Sfeir wrote:

> Sorry should have mentioned the exception is:
>
> org.springframework.jdbc.UncategorizedSQLException: OJB operation:  
> encountered SQLException [Wrong data type: Timestamp format must be  
> yyyy-mm-dd hh:mm:ss.fffffffff]; nested exception is  
> java.sql.SQLException: Wrong data type: Timestamp format must be  
> yyyy-mm-dd hh:mm:ss.fffffffff
> java.sql.SQLException: Wrong data type: Timestamp format must be  
> yyyy-mm-dd hh:mm:ss.fffffffff
>
> I'm using hsqldb 1.7.3.
>
> R
>
> On Jun 4, 2005, at 9:09 AM, Robert S. Sfeir wrote:
>
>
>> Hey guys,
>>
>> I've been trying to figure out if this is something OJB is doing  
>> or something Spring Framework's hooks are doing.
>>
>> I have a definition of a field as follows:
>>
>>          <field-descriptor
>>             name="submissionDate"
>>             column="ticket_submissionDate"
>>             jdbc-type="TIMESTAMP"
>>              
>> conversion="org.apache.ojb.broker.accesslayer.conversions.JavaDate2Sq 
>> lTimestampFieldConversion"
>>             >
>>         </field-descriptor>
>>
>> The data incoming is a long and the Object is an instace of Date,  
>> which according to the converting class is correct.  After doing  
>> more stepping through the code in the debugger, I noticed that the  
>> conversion class never gets called.  I even set it to something  
>> completely ridiculous and nothing failed.
>>
>> So the question is, did something fall off here in the move to ojb  
>> 1.0.3 or is this something I should take up with Juergen on the  
>> Spring list?
>>
>> Thanks
>> R
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
>> For additional commands, e-mail: ojb-dev-help@db.apache.org
>>
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
> !DSPAM:42a1aadb228204342178072!
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org


Re: SQL Conversion not working in 1.0.3???

Posted by "Robert S. Sfeir" <ro...@codepuccino.com>.
Sorry should have mentioned the exception is:

org.springframework.jdbc.UncategorizedSQLException: OJB operation:  
encountered SQLException [Wrong data type: Timestamp format must be  
yyyy-mm-dd hh:mm:ss.fffffffff]; nested exception is  
java.sql.SQLException: Wrong data type: Timestamp format must be yyyy- 
mm-dd hh:mm:ss.fffffffff
java.sql.SQLException: Wrong data type: Timestamp format must be yyyy- 
mm-dd hh:mm:ss.fffffffff

I'm using hsqldb 1.7.3.

R

On Jun 4, 2005, at 9:09 AM, Robert S. Sfeir wrote:

> Hey guys,
>
> I've been trying to figure out if this is something OJB is doing or  
> something Spring Framework's hooks are doing.
>
> I have a definition of a field as follows:
>
>          <field-descriptor
>             name="submissionDate"
>             column="ticket_submissionDate"
>             jdbc-type="TIMESTAMP"
>              
> conversion="org.apache.ojb.broker.accesslayer.conversions.JavaDate2Sql 
> TimestampFieldConversion"
>             >
>         </field-descriptor>
>
> The data incoming is a long and the Object is an instace of Date,  
> which according to the converting class is correct.  After doing  
> more stepping through the code in the debugger, I noticed that the  
> conversion class never gets called.  I even set it to something  
> completely ridiculous and nothing failed.
>
> So the question is, did something fall off here in the move to ojb  
> 1.0.3 or is this something I should take up with Juergen on the  
> Spring list?
>
> Thanks
> R
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: ojb-dev-help@db.apache.org
>
>
> !DSPAM:42a1a8af171574298925553!
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org