From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | stev knowles <stev(at)Precision(dot)Guesswork(dot)COM> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: no value in string |
Date: | 2002-06-10 20:54:27 |
Message-ID: | 8697.1023742467@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
stev knowles <stev(at)Precision(dot)Guesswork(dot)COM> writes:
> so, it appears that my empty strings are really strings with a single blank
> space. how can i stop that from happening when i load the data in? is there
> some way to declare the datum so that blank values are not turned into a
> space?
PG is certainly not doing that to you (unless perhaps you are talking
about a char(1) column). You need to look for the cause in your
client-side code.
If you are asking for a way to defend against client-side brain death,
perhaps a constraint on the order of CHECK (foo != ' ') would do.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuchs | 2002-06-11 08:55:46 | string functions |
Previous Message | stev knowles | 2002-06-10 19:27:53 | no value in string |