On Tue, Feb 24, 2004 at 09:16:59PM -0000, Aaron Stone wrote: > "Paul F. De La Cruz" <[EMAIL PROTECTED]> said: > [huge snip of almost everything] > > > internal_date TIMESTAMP WITHOUT TIME ZONE, > > As long as this doesn't cause pre-7.1 version of PostgreSQL to choke, the > change should definitely be made before 2.0rc3!
I think it would make the pre-7.1 versions of PostgreSQL choke as they either only have timestamp (without the additional 'with/without time zone' or use some other strange format. I'm thinking that this may be a problem that's been around for awhile and just wasn't noticed since PostgreSQL seems to give dates different from what date_sql2imap is looking for. I'm no PostgreSQL expert though so if someone knows otherwise concerning older PG versions, then by all means speak up. > Also, what about adding more sanity/format checking to the various scripts and > date access functions? I bet that it wouldn't be too hard to code something up > that handled a mangled date better. Perhaps something as simple as a forced > date format conversion in the SELECT statement, allowing almost any underlying > format to be used by the database... Hmm... I wonder if it'd be best to have the database return the date in an intermediary format (epoch timestamp?) and then convert from that since we'd could (hopefully) trust it to be the same no matter what database was used? Blessings in Jesus, Paul F. De La Cruz
