Hello Anand:
Thanks for the input.
The problem turned out to be date fields with null values. Disappointing!
A lot of my Sybase procedures tested for null dates.
So my workaround was to edit the null dates to a pseudo date. This is least
got my database poplulated. Will try the cast for queries and updates.
I don't know which SQL, Postresql or Sybase, is an extension or non-compliant.
Bill Barnes
>===== Original Message From "Anand Raman" <araman@india-today.com> =====
>HI bill
>Try to cast the field to the datetime type
>
>'ur_string_goes_here'::datetime
>
>Hope this will help
>Anand Raman
>
>----- Original Message -----
>From: Bill Barnes <bbarnes@operamail.com>
>To: <pgsql-general@postgresql.org>
>Sent: Friday, April 28, 2000 6:09 PM
>Subject: [GENERAL] date format problem
>
>
>> Hello List:
>>
>> Using 6.5.3 on SuSE 6.4.
>>
>> Built a table with a date field as type 'datetime'.
>>
>> I try to copy a text file to the table and get a 'bad date format'
>> Dates in the text file may be null, but are in the form 1997-12-15.
>> Have tried several of the date field types with the same result.
>> The copy executes properly if I redefine the date field to varchar.
>>
>> Thanks for your help.
>> Bill Barnes
>>
>> ------------------------------------------------------------
>> This e-mail has been sent to you courtesy of OperaMail, a
>> free web-based service from Opera Software, makers of
>> the award-winning Web Browser - http://www.operasoftware.com
>> ------------------------------------------------------------
>>
------------------------------------------------------------
This e-mail has been sent to you courtesy of OperaMail, a
free web-based service from Opera Software, makers of
the award-winning Web Browser - http://www.operasoftware.com
------------------------------------------------------------
