Documentation of maximum input string lengths - Mailing list pgsql-hackers

From Gavin Sherry
Subject Documentation of maximum input string lengths
Date
Msg-id Pine.LNX.4.21.0208260105230.22485-100000@linuxworld.com.au
Whole thread Raw
Responses Re: Documentation of maximum input string lengths  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Hi all,

I've just been thinking that the documentation doesn't cover the maximum
input string lengths for various data types well. Case in point, the
date/time code: there was a fair amount of discussion about validation
input, including checking for 'unreasonable' string lengths. Unless you
went and poked around the code, you couldn't know that the maximum string
length for a date/time string is 52 bytes.

So, the question is this: should there be documentation of the maximum
string length of a data structure so that application programmers can
provide string length validation? Perhaps MAXDATELEN and other static
values in adt/ should be put in pg_config.h so that the user does not need
to hard code them? Perhaps it is a bad idea, since programmers should also
do other validation, such as ensuring that a submitted date/time value
is what the program(mer) is expecting?

Gavin




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Are "text" strings 0 terminated internally?
Next
From: sugita@sra.co.jp
Date:
Subject: Re: Mac OS X: system shutdown prevents checkpoint