Andreas Joseph Krogh andr...@officenet.no wrote:
ERROR: null value in column created violates not-null constraint
It is easy to add the table name to the message, but ...
ERROR: null value in column public.mytable.created violates not-null
constraint
Oracle does this btw...
Do we have
On Tuesday 12. January 2010 11.10.09 Takahiro Itagaki wrote:
Andreas Joseph Krogh andr...@officenet.no wrote:
ERROR: null value in column created violates not-null constraint
It is easy to add the table name to the message, but ...
ERROR: null value in column public.mytable.created
Takahiro Itagaki itagaki.takah...@oss.ntt.co.jp writes:
Do we have any guideline about the message for identifier names?
The issue has come up before. I think that what we really need here is
to implement additional fields in error message reports, so that the
name and schema name of the
On Tue, Jan 12, 2010 at 5:10 AM, Takahiro Itagaki
itagaki.takah...@oss.ntt.co.jp wrote:
Andreas Joseph Krogh andr...@officenet.no wrote:
ERROR: null value in column created violates not-null constraint
It is easy to add the table name to the message, but ...
ERROR: null value in column
Robert Haas robertmh...@gmail.com wrote:
I feel like we ought to be doing this in a way where the output is
properly escaped. Right now:
Yeah, that's been an occasional irritation for me, even though I
don't actually use quote characters in any of my quoted identifiers.
Also, tab-completion
Robert Haas robertmh...@gmail.com writes:
I feel like we ought to be doing this in a way where the output is
properly escaped.
This is one of several reasons why code shouldn't be trying to scrape
the names out of the human-readable message.
regards, tom lane
--
Sent
Hi all, when trying to insert/update a NOT NULL column with a null-values (in
this case the created-column), we get this error:
ERROR: null value in column created violates not-null constraint
Using JDBC this error-message is what appears in the SQLException.getMessage()
which makes it
