| From: | "Usama Dar" <munir(dot)usama(at)gmail(dot)com> |
|---|---|
| To: | "Andrew Chernow" <ac(at)esilo(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers list" <pgsql-hackers(at)postgresql(dot)org>, "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
| Subject: | Re: timetz range check issue |
| Date: | 2007-12-25 16:57:42 |
| Message-ID: | ff0e67090712250857n24f9b804v864cb0e739df6df3@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Dec 22, 2007 7:40 PM, Andrew Chernow <ac(at)esilo(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | imad | 2007-12-25 17:12:23 | Re: Binary data type with other output method |
| Previous Message | Andrew Dunstan | 2007-12-25 16:10:25 | Re: Binary data type with other output method |