Re: Boolean casting in 7.3 -> changed?

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "David Wheeler" <david(at)wheeler(dot)net>, "David Walker" <pgsql(at)grax(dot)com>
Cc: "PostgreSQL Development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Boolean casting in 7.3 -> changed?
Date: 2002-11-30 20:24:21
Message-ID: 03AF4E498C591348A42FC93DEA9661B8128CC3@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: David Wheeler [mailto:david(at)wheeler(dot)net]
> Sent: 30 November 2002 20:18
> To: David Walker
> Cc: PostgreSQL Development
> Subject: Re: [HACKERS] Boolean casting in 7.3 -> changed?
>
>
> On Wednesday, November 27, 2002, at 04:34 PM, David Walker wrote:
>
> > Does this mean that in the future '342' may not be valid as
> an insert
> > into a
> > numeric field and that we should be using 342 instead?
>
> I didn't see an answer to this question, but I sincerely hope
> that the
> answer is
> "no." Otherwise, dynamic interfaces are going to have a much harder
> time.

pgAdmin will have similar problems. I can work round it for standard
types, but how will I tell whether a custom type will reject quoted
values?

Regards, Dave.

Browse pgsql-hackers by date

  From Date Subject
Next Message Jason E. Stewart 2002-11-30 20:43:04 Re: ANNOUNCE: DBD::Pg 1.20
Previous Message Dan Langille 2002-11-30 20:19:09 Re: 7.4 Wishlist