db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "anon permutation" <anonpermutat...@hotmail.com>
Subject torque 3.1 incompatibility with PostgreSQL
Date Tue, 21 Oct 2003 06:27:50 GMT

Hi,

I have tried posting this potential bug on the users list, but I have not 
gotten any response.  Can you give me some pointers?  Am I doing something 
wrong, or is this a bug?

I have encountered a problem when using Torque 3.1 with PostgreSQL, and I am 
trying to verify that this is an actual bug.

When using Torque 3.0, a select statement that uses a Timestamp column will 
be generated as something like this (edited the sql to make this mail 
shorter):

select * FROM instru_intraday
WHERE (instru_intraday.SAMPLE_DATE>{ts '2003-09-17 00:00:00.0'} AND 
instru_intraday.SAMPLE_DATE<{ts '2003-10-15 18:14:35.721'})

This works fine.

However, when using Torque 3.1, something like this is generated:

This (simplified) sql statement is generated:
SELECT * FROM instru_intraday WHERE
(instru_intraday.SAMPLE_DATE>'20030916000000' AND
instru_intraday.SAMPLE_DATE<'20030918152213')

PostgreSQL will complain about --  Bad timestamp external
representation '20030916000000'

Have you seen something like this?  Thanks.

_________________________________________________________________
Surf and talk on the phone at the same time with broadband Internet access. 
Get high-speed for as low as $29.95/month (depending on the local service 
providers in your area).  https://broadband.msn.com


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


Mime
View raw message