We always truncate our date fields before inserting and updating as a rule
so that the database has 00:00:00 for the time component.
--
Matt Brennan
SQL*Tools Specialist
GERS Retail Systems
9725-C Scranton Road
San Diego, California 92121
1-800-854-2263
mbrennan_at_gers.com
(Original email address is spam-blocked.)
Chad Whitney <raven_at_WPI.EDU> wrote in article
<6ogiks$can$1_at_bigboote.WPI.EDU>...
> To all those making 3.0 compliant:
> I have found a problem that is/has been irritating me for a about a
> week. Here is the situation:
> When doing an insert into the database, one of my fields, having the
> default value $$DATETIME$$, puts in a time stamp. This is fine, as the
> application does not use timestamps. However, when I go to query for the
> record, it is unable to return it because the following SQL is sent to
the
> DB:
> select unit_meas_id, unit_meas_desc, revision_date, whole_flag
> from unit_meas
> where (REVISION_DATE = to_date('01-JAN-2000 00:00:00', 'DD-MON-YYYY
> HH24:MI:SS')
>
> The issue is that if the record has a REVISIOn_DATE value of:
> 01-JAN-2000 02:02:01
> the query does not work.
> Does anyone know/have a suggestion as to how I can truncate the time from
> the date? The difficulty lies in how to force the form to explicitly
send
> the correct SQL to the database. Because REVISION_DATE is of datatype
> DATETIME, it forces the where clause, which is inaccurate.
> Thanks in advance,
>
> Chad Whitney
> IS Analyst
> GTE Government Systems
> Chad.Whitney_at_gsc.gte.com
> or
> raven_at_wpi.edu
>
Received on Tue Jul 14 1998 - 17:21:21 CDT
