Mailing-List: contact torque-user-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Torque Users List" <torque-user@db.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C81480.F579C02B"
Subject: generated SQL criteria using date comparison does not work with
	MaxDB: {ts XXX} instead of {d XXX}
Date: Mon, 22 Oct 2007 09:55:48 +0200
Message-ID: <D46D61F2B36A854EBDFF4A980DC91B9639F914@uny-srv-ex.unycom.com>
Thread-Topic: generated SQL criteria using date comparison does not work
	with MaxDB: {ts XXX} instead of {d XXX}
Thread-Index: AcgUgPUdH6NFw2awSUmaeleZIUgicw==
From: "Alexander Zimmer" <alexander.zimmer@unycom.com>
To: <torque-user@db.apache.org>

------_=_NextPart_001_01C81480.F579C02B
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hello list,

=20

I'm using Torque 3.3 with SAP's MaxDB 7.5.

=20

This is what I want to do:

-----------------------------------

  Criteria criteria =3D new Criteria();

  criteria.add(OrdersPeer.DELIVERY_DATE, cal.getTime(),
Criteria.LESS_EQUAL);

=20

This should bring up all rows with a "DELIVERY DATE" of max. the date in
the calender object "cal". The column DELIVERY DATE ist DATE column (not
timestamp). Thus, it should be rendered as:

  SELECT DISTINCT ORDERS.ORDER_ID FROM ORDERS WHERE
ORDERS.DELIVERY_DATE<=3D{d '2007-10-29'}

=20

which would work fine.

=20

The problem:

----------------

However, Torque generates this constraint (only difference is the use of
{ts XXX} instead of {d XXX}):

=20

  SELECT DISTINCT ORDERS.ORDER_ID FROM ORDERS WHERE
ORDERS.TARGET_DELIVERY_DATE<=3D{ts '2007-10-29 09:35:09.556'}

=20

Unfortunately, this leaves me with an internal MaxDB error: move error.
Don't ask me why the error message is apparently unrelated to the
problem, I tried do execute this query in a MaxDB client and found that
if I change the constraint to a pure date-wise comparison (as shown
above) it would work.

=20

=20

=20

Is this a known issue? I am not 100% sure if this in fact is a MaxDB
error? IMHO it should work with timestamps as well. Anyway, if Torque
would use date comparison ({d XXX} instead of {ts XXX}), it would work
too. How can I get this to work?

=20

TIA,

Alex


------_=_NextPart_001_01C81480.F579C02B--