| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Add error-checking to timestamp_recv |
| Date: | 2004-05-20 16:56:45 |
| Message-ID: | 200405201656.i4KGuj226447@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > I wasn't aware you could throw binary values into the timestamp fields
> > like that. I thought you needed to use a C string for the value.
>
> This facility was added in 7.4 as part of the wire-protocol overhaul.
> It's nothing directly to do with PREPARE; you could get the same result
> with no prepared statement using PQexecParams.
Ah, no wonder I had not seen that before. So, I guess the issue is how
much error checking do we want to have for these binary values. I was a
little disturbed to hear he could insert data he couldn't later view.
How many datatype have this issue?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2004-05-20 17:01:55 | Re: Add error-checking to timestamp_recv |
| Previous Message | Tom Lane | 2004-05-20 16:44:36 | Re: Add error-checking to timestamp_recv |