BUG #1759: domain check constraint ignored in prepared statement - Mailing list pgsql-bugs

From Boris Sukholitko
Subject BUG #1759: domain check constraint ignored in prepared statement
Date
Msg-id 20050707140847.471C1F0CBE@svr2.postgresql.org
Whole thread Raw
Responses Re: BUG #1759: domain check constraint ignored in prepared statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
The following bug has been logged online:

Bug reference:      1759
Logged by:          Boris Sukholitko
Email address:      bobatonhu@yahoo.co.uk
PostgreSQL version: 7.4.8
Operating system:   Linux
Description:        domain check constraint ignored in prepared statement
Details:

Hi,

It seems that the domain check constraint does not trigger
an error when using prepared statement in perl's DBD::Pg 1.42.

It seemed to work in earlier versions of DBD::Pg module.

The following code snippet manifests the problem:
#!/usr/bin/perl -w
use strict;
use DBI;
use DBD::Pg;

my $dbh = DBI->connect("dbi:Pg:dbname=testdb");
$dbh->do(<<ENDS);
create domain display_text_d text
        constraint display_text_d_non_empty_chk check (VALUE ~
'[a-zA-z0-9]');
create table domain_test (d display_text_d not null);
ENDS

my $s = $dbh->prepare("insert into domain_test (d) values (?)");

# This execute will succeed leaving invalid value
# in the database
$s->execute(' ');

# This statement fails due to the check constraint
# as expected
$dbh->do("insert into domain_test (d) values (?)", undef, ' ');

Thanks,
Boris.

pgsql-bugs by date:

Previous
From: Denis Vlasenko
Date:
Subject: Re: BUG #1756: PQexec eats huge amounts of memory
Next
From: "Steve Bennett"
Date:
Subject: BUG #1757: timestamp 'epoch' is not absolute