[ic] "bad timestamp external representation"?
interchange at ericsmall.com
Tue Jul 27 18:50:39 EDT 2004
Janine Sisk wrote:
> 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?
I think it some sort of problem with the timestamp value being truncated
to 8 bytes when it is in it's string representation. 8 bytes is the
size of a timestamp field in PostgreSQL.
My hunch is that either Interchange or DBI is taking the timestamp,
treating it like a string and truncating it to 8 characters so that it
fits into 8 bytes. Postgres doesn't like this now invalid timestamp
string and returns an error. Then Interchange, now thinking that
Postgres screwed up, also returns an error.
I switched to MySQL for a different reason than this problem. The issue
I had was that Interchange didn't seem to like Postgres numeric fields.
Seemed like every field had to be text.
More information about the interchange-users