On Dec 22, 2007 7:40 PM, Andrew Chernow <[EMAIL PROTECTED]> wrote:
> >Tom Lane wrote:
> >>range-checks are present only where needed for the backend to defend
> itself
>
> Survival is very important, but so is maintaining data integrity. IMHO,
> data
> validation should be as consistent as poss
>Tom Lane wrote:
>>range-checks are present only where needed for the backend to defend itself
Survival is very important, but so is maintaining data integrity. IMHO, data
validation should be as consistent as possible. If the backend refuses data on
one hand but allows it on the other, confu
Andrew Chernow <[EMAIL PROTECTED]> writes:
> I think a range check is needed in timetz_recv & time_recv.
I think that the design philosophy for the binary I/O code is to be as
fast as safely possible, and accordingly range-checks are present only
where needed for the backend to defend itself. Is
When inserting a timetz in binary mode, there are no range checks on the time
value (nor on the zone). In text mode, things are fine:
postgres=# insert into t values ('24:00:00.01-05'::timetz);
ERROR: date/time field value out of range: "24:00:00.01-05"
// 24:00:00.01-05
double d
