Would you show an example of the invalid value this is trying to avoid? ---------------------------------------------------------------------------
Stephen Frost wrote: > Greetings, > > The attached patch adds some error-checking to the timestamp_recv > function so that it's not possible to put an invalid timestamp into a > timestamp column (hopefully). The check is done in basically the > exact same way the out-of-bounds check in timestamp2tm is done. > There's probably an easier/cleaner way but this should work or at > least generate discussion and a better patch. :) > > Thanks, > > Stephen [ Attachment, skipping... ] > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
