Re: [ic] "bad timestamp external representation"?

[Janine Sisk <suppressed>]

Resending....

Well, I've narrowed it down a bit.  The error log shows this:

63.69.52.133 EpZsCaBB:63.69.52.133 - [27/July/2004:16:14:21 -0400] shop  
/cgi-bin/shop/process Vend::Table::DBI - Length Exception! - Data  
length: 25 Field length: 8
63.69.52.133 EpZsCaBB:63.69.52.133 - [27/July/2004:16:14:21 -0400] shop  
/cgi-bin/shop/process Vend::Table::DBI - Length Exception - Table:  
orderline, Field: update_date. Action to take: truncate_log
63.69.52.133 EpZsCaBB:63.69.52.133 - [27/July/2004:16:14:21 -0400] shop  
/cgi-bin/shop/process Runtime error: DBD::Pg::st execute failed: ERROR:  
 Bad timestamp external representation '2004-07-' at  
/usr/lib/interchange/lib/Vend/Table/DBI.pm line 1626.

So it gets a very long date string from somewhere, truncates it to the  
expected length, and then gets an error inserting it because it's no  
longer a valid date.

The default date format in Postgres is very long, and that's probably  
the culprit:

shop=> select now();
              now
-------------------------------
 2004-07-27 16:22:30.469621-04
(1 row)

MySQL, according to a book I happened to have handy, has a default  
format of YYYYMMDDHHMMSS, which would truncate into 8 characters that  
actually work as  a date.

I can't find any way of telling Postgres to use that date format.  Does  
this mean Interchange isn't really compatible with Postgres after all,  
or am I missing something here?

thanks,

janine

On Jul 27, 2004, at 1:31 PM, Eric Small wrote:

> Janine Sisk wrote:
> > HI all,
> > Thanks for all the GPG help, i finally did get it working smoothly.
> > Now we have a new problem.  The client says that he's getting these  
> > errors when trying to mark orders as shipped:
> > 63.69.52.133 EpZsCaBB:63.69.52.133 - [27/July/2004:12:18:06 -0400]  
> > shop /cgi-bin/shop/process Runtime error: DBD::Pg::st execute failed:  
> > ERROR:  Bad timestamp external representation '2004-07-' at  
> > /usr/lib/interchange/lib/Vend/Table/DBI.pm line 1626.
> > >
> > 63.69.52.133 EpZsCaBB:63.69.52.133 - [27/July/2004:12:19:44 -0400]  
> > shop /cgi-bin/shop/admin/order Vend::Table::DBI - Length Exception! -  
> > Data length: 25 Field length: 8
>
> I ran into that problem quite recently.
> See my post from 6/30/04
> http://www.icdevgroup.org/pipermail/interchange-users/2004-June/ 
> 039780.html
>
> I never got any responses to my post about it and the only "fix" I  
> came up with on my own was to switch to MySQL.
>
> I did find a workaround for PostgreSQL though, which is detailed in my  
> earlier post.
>
> Sorry I can't be of more help,
> Eric
>
> --
> Interchange 5.2.0 / Debian 3.0 Stable / MySQL 4.0.20-log
> _______________________________________________
> interchange-users mailing list
> suppressed
> http://www.icdevgroup.org/mailman/listinfo/interchange-users

_______________________________________________
interchange-users mailing list
suppressed
http://www.icdevgroup.org/mailman/listinfo/interchange-users