1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
libdbd-pg-perl (3.14.0-1) unstable; urgency=medium
From upstream Changes for 3.14.0:
- The $dbh->primary_key_info and $dbh->foreign_key_info methods will now
always return a statement handle, even with no matches. Previously, they
returned undef directly. Callers can check if the returned handle contains
any rows.
- The $dbh->tables method will always return a list, even if it is empty.
- Removed the long-deprecated _pg_use_catalog method.
-- gregor herrmann <gregoa@debian.org> Mon, 20 Jul 2020 17:47:15 +0200
libdbd-pg-perl (3.0.0-1) unstable; urgency=medium
From upstream Changes:
- Major change in UTF-8 handling. If client_encoding is set to UTF-8,
always mark returned Perl strings as utf8. See the pg_enable_utf8 docs
for more information.
-- gregor herrmann <gregoa@debian.org> Wed, 12 Feb 2014 19:32:53 +0100
libdbd-pg-perl (1.42-1) unstable; urgency=low
DBD::Pg changed its behaviour concerning the use of placeholders. It
implements now server side placeholders, this is more efficient but has the
drawback of being more strict in the syntax of placeholder as it must
match what PostgreSQL will accept.
Here are some examples of things which used to be accepted and which aren't
any more (you can easily extrapolate for other types):
SELECT ... WHERE pdate > now() - interval ?
SELECT inet ?
The correct queries are:
SELECT ... WHERE pdate > now() - ?::interval
SELECT ?::inet
If you don't want to replace the queries, a simple work around is to disable
the server side queries with:
$dbh->{pg_server_prepare} = 0;
Some useful links can be found in the bug report #315708:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=315708;msg=86
-- Raphael Hertzog <hertzog@debian.org> Mon, 13 Nov 2006 22:05:02 +0100
|
