From: | Mike Mascari <mascarm(at)mascari(dot)com> |
---|---|
To: | "Wm(dot) G(dot) Urquhart" <wgu(at)wurquhart(dot)co(dot)uk> |
Cc: | PostgreSQL General Forum <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Violation of NOT NULL |
Date: | 2002-05-23 14:42:14 |
Message-ID: | 3CECFFC6.B70AF8C8@mascari.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom Lane wrote:
>
> "Wm. G. Urquhart" <wgu(at)wurquhart(dot)co(dot)uk> writes:
> > I have a table where I've set two of the columns (varchar()) to be NOT
> > NULL. However, PostgreSQL allows me to enter rows without valid data for
> > these columns when I use a Stored Function.
>
> I don't really believe this, and I'm certainly not likely to be able to
> reproduce it with nothing but an INSERT to go on. Please provide a
> *complete* example, preferably in the form of a script that can be fed
> to psql to exhibit the problem starting from an empty database.
Also, if by chance you are coming over from Oracle and expect an empty
string to be treated as NULL, it is not...
Mike Mascari
mascarm(at)mascari(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Nigel J. Andrews | 2002-05-23 14:46:23 | Postgres under CygWin |
Previous Message | Ron Snyder | 2002-05-23 14:41:20 | Re: Process balancing on smp db server/apache web serve |