Re: timetz range check issue - Mailing list pgsql-hackers

From Usama Dar
Subject Re: timetz range check issue
Date
Msg-id ff0e67090712250857n24f9b804v864cb0e739df6df3@mail.gmail.com
Whole thread Raw
In response to Re: timetz range check issue  (Andrew Chernow <ac@esilo.com>)
List pgsql-hackers


On Dec 22, 2007 7:40 PM, Andrew Chernow <ac@esilo.com> 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 possible.  If the backend refuses data on
one hand but allows it on the other, confusion sets in.  I realize that binary
input can't always be 100% validated, but a best effort is good form.

+1




--
Usama Munir Dar http://www.linkedin.com/in/usamadar
Consultant Architect
Cell:+92 321 5020666
Skype: usamadar

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Binary data type with other output method
Next
From: imad
Date:
Subject: Re: Binary data type with other output method