Re: Possible bug? WAS :Bad (null) varchar() external representation.

From: Justin Clift <aa2(at)bigpond(dot)net(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: Possible bug? WAS :Bad (null) varchar() external representation.
Date: 2001-01-12 02:27:39
Message-ID: 3A5E6B9B.2E45D429@bigpond.net.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Hi Tom,

I think you are right. It does seem to barf on NULLS and
length(varchar), regardless.

Thanks for your assistance.

BTW - How do things normally get added to the FAQ? I would like to add
something about length(varchar) and NULLS not working in PostgreSQL
7.0.x

Regards and best wishes,

Justin Clift
Database Administrator

Tom Lane wrote:
>
> Justin Clift <aa2(at)bigpond(dot)net(dot)au> writes:
> > I haven't seen a mention of a maximum number of constraints of similar
> > applying to a table. If so, then could someone please point me to it...
>
> There is no such limit that I know of.
>
> > Yet if I remove BOTH the "staff_details_phone_three" &
> > "staff_details_managers_notes" constraints it works :
>
> Are you absolutely certain that that's how it went? I think the most
> likely story is just that you were hitting the length(varchar)-barfs-
> on-NULL bug, and got confused about which combinations you'd tried.
>
> regards, tom lane

In response to

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2001-01-12 02:50:04 Re: Possible bug? WAS :Bad (null) varchar() external representation.
Previous Message Tom Lane 2001-01-12 00:36:18 Re: "SELECT" problem on 7.0.3