Some quick research on this indicated that this seems
to be a problem with the JDBC Timestamp API which does
not allow for the TimeZone part of the SQL data. My
guess is that JDBC drivers for SQL servers that support
this column type convert this into the correct GMT
time representation or supply
If I didn't need to do this I wouldn't be asking. :)
I was hoping to avoid overriding/adding methods to do a conversion, the
whole point is to have Torque handle this automatically.
Raul
On Wed, 2008-01-02 at 16:34 -0500, Greg Monroe wrote:
> Some quick research on this indicated that this seem
TORQUE 3 is genetarting for SQL Server the date in the format: '20070130
00:00:00' but SQL Server 2005 is not working with this format. Is posible
change the output date format in TORQUE?
2008/1/4, Raul Acevedo <[EMAIL PROTECTED]>:
>
> If I didn't need to do this I wouldn't be asking. :)
>
> I wa
