On Mon, 2006-01-30 at 20:45 -0500, Tom Lane wrote:
> You only fixed the bind-parameter case, though, no? The problem is
> still rampant in the PLs.
Right: the bug report was specific to the bind parameter case. Domain
constraints should also be checked before returning values of a domain
type fro
Neil Conway <[EMAIL PROTECTED]> writes:
> On Sat, 2006-01-28 at 20:17 +0100, Peter Eisentraut wrote:
>> This bug was reported to Debian. Comments?
> AFAICS I fixed this a few weeks ago (post-8.1.2):
You only fixed the bind-parameter case, though, no? The problem is
still rampant in the PLs.
On Sat, 2006-01-28 at 20:17 +0100, Peter Eisentraut wrote:
> This bug was reported to Debian. Comments?
AFAICS I fixed this a few weeks ago (post-8.1.2):
http://archives.postgresql.org/pgsql-committers/2006-01/msg00209.php
http://archives.postgresql.org/pgsql-patches/2006-01/msg00139.php
I get
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> This bug was reported to Debian. Comments?
These are all known issues. The implementation of domains really needs
rather a lot of work :-(.
One thing we might think about is having domain types use a special set
of input functions rather than just
This bug was reported to Debian. Comments?
Tim Southerwood wrote:
> Package: postgresql-8.1
> Version: 8.1.2-1
> Severity: important
>
> DOMAIN CHECK constraint is bypassable when inserting rows using
> perl/DBD::Pg AND prepare/execute semantics AND using bind values.
>
> This is serious as data
