Christopher Kings-Lynne [EMAIL PROTECTED] writes:
I'm still getting failure, but it gets weirder:
Fixed --- turns out the bug is that timetz_out was scribbling on its
input (thereby changing the table) in the --enable-integer-datetimes
path.
I back-patched the change into 7.3, although I
Oops - just to clarify I accidentally copied too many INSERTs into the
email. The result of the first SELECT is correct compared to the INSERTs
that I did. I copied the INSERTs and CREATE TABLE as-is from timetz.sql
Chris
-Original Message-
From: Christopher Kings-Lynne
Christopher Kings-Lynne [EMAIL PROTECTED] writes:
What the heck!!?!?!?! The SELECT statement has somehow edited
the data in the table or something??? From this point forward,
the table is all stuffed...
Hm, time to dig out the debugger and figure out where the breakage
is. Do you want to do
