> 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?
> If you mean blank like '', then if the field is a string, it
> would be normal behavior as is.
Yes, they are strings (varchar). Know the best way to handle it?
In response to
pgsql-general by date
|Next:||From: Dennis Gearon||Date: 2003-04-28 18:21:08|
|Subject: Re: Selecting the most recent date|
|Previous:||From: David Link||Date: 2003-04-28 17:52:15|
|Subject: Re: pq_recvbuf: unexpected EOF |