| From: | Dennis Gearon <gearond(at)cvc(dot)net> |
|---|---|
| To: | Robert Fitzpatrick <robert(at)webtent(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Setting a field to default if blank value |
| Date: | 2003-04-28 23:05:14 |
| Message-ID: | 3EADB3AA.1030905@cvc.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
did you try what I gave you? It should have puked when you tried to insert a blank field.
Robert Fitzpatrick wrote:
> Looking for the best way of handling this, would like to do it in the
> database and not in my apps. I set a field to 'Not Null', but if a blank
> value comes in, the field will accept it as just that, a blank string.
> How can avoid this using a trigger or function? I thought about a
> function that would check the field and then place a trigger, but that
> gets to be a lot of functions and triggers for different fields. Is
> there a way to pass a field name to the function? (in plpgsql)
>
> Or what is the best way to handle this for many different fields in many
> tables?
>
> --
> Robert
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Crawford | 2003-04-28 23:11:34 | Re: adding times togeather |
| Previous Message | Tom Lane | 2003-04-28 23:04:12 | Re: timestamps and dates |