History log of /PHP-7.4/ext/pdo_pgsql/pgsql_statement.c (Results 101 – 125 of 147)
Revision (<<< Hide revision tags) (Show revision tags >>>) Date Author Comments
Revision tags: php-5.2.1RC1
# 2d4b8e19 28-Nov-2006 Ilia Alshanetsky

Fixed bug #39656 (crash when calling fetch() on a PDO statment object
after closeCursor()).


# c7d84b74 16-Nov-2006 Ilia Alshanetsky

Fixed compiler warnings


Revision tags: php-5.2.0, php-5.2.0RC6, php-5.2.0RC5
# 2332e4f9 19-Sep-2006 Ilia Alshanetsky

Fixed bug #37870 (pgo_pgsql tries to de-allocate unused statements).
Fixed bug #36681 (pdo_pgsql driver incorrectly ignored some errors).
Fixed test for bug #38253 not to use faulty SQL that

Fixed bug #37870 (pgo_pgsql tries to de-allocate unused statements).
Fixed bug #36681 (pdo_pgsql driver incorrectly ignored some errors).
Fixed test for bug #38253 not to use faulty SQL that generates errors in
PostgreSQL

show more ...


Revision tags: php-5.2.0RC4, php-5.2.0RC3, php-5.1.6, php-5.2.0RC2, php-5.1.5, php-4.4.4, php-4.4.4RC1, php-5.1.5RC1
# 7f526717 01-Aug-2006 Ilia Alshanetsky

Fixed bug #38168 (Crash in pdo_pgsql on missing bound parameters).


Revision tags: php-4.4.3, php-5.2.0RC1, php-4.4.3RC2, BEFORE_NEW_OUTPUT_API, php-4.4.3RC1
# 79ebfe38 08-May-2006 Ilia Alshanetsky

Fixed memory leaks when working with cursors in PDO PostgreSQL driver.


Revision tags: php-5.1.4, RELEASE_1_0_3, php-5.1.3, php-5.1.2, RELEASE_1_3, php-5.1.3RC3, php-5.1.3RC2
# fb7d5bd7 27-Mar-2006 Wez Furlong

The fix for #35332 caused #35671 (and thus PECL #6504).

Partially back out that fix and introduce an extra optional step for drivers to
canonicalize the "name" that is used for registeri

The fix for #35332 caused #35671 (and thus PECL #6504).

Partially back out that fix and introduce an extra optional step for drivers to
canonicalize the "name" that is used for registering parameters.

show more ...


# 7731dc94 17-Mar-2006 Antony Dovgal

fix #36727 (segfault in pdo_pgsql bindValue() when no parameters are defined)


Revision tags: php-5.1.3RC1, RELEASE_1_2, RELEASE_0_9_4, RELEASE_1_0_4, php-4.4.2, php-5.1.2RC2, php-4.4.2RC2
# 5bd93221 01-Jan-2006 foobar

bump year and license version


Revision tags: php-5.1.2RC1
# f7276af1 17-Dec-2005 Ilia Alshanetsky

Fixed compiler warning


# c2ed71a8 17-Dec-2005 Ilia Alshanetsky

Retry on failed prepare resulting from duplicate statement name.


Revision tags: RELEASE_1_1_1, RELEASE_1_1, RELEASE_1_0, RELEASE_2_0_2
# 4e03ce9f 01-Dec-2005 Ilia Alshanetsky

Fixed memory leaks


# 911355be 30-Nov-2005 Ilia Alshanetsky

Fixed memory leak


# 13103335 29-Nov-2005 Wez Furlong

Added PDO::pgsqlLOBCreate(), PDO::pgsqlLOBOpen() and PDO::pgsqlLOBUnlink().


Revision tags: php-5.1.1
# 70331c36 25-Nov-2005 Wez Furlong

Addresses #35338.

Postgres client API is pretty poor, so we have zero idea about the actual
parameter types in a statement.

We now defer the preparation of a statement until the

Addresses #35338.

Postgres client API is pretty poor, so we have zero idea about the actual
parameter types in a statement.

We now defer the preparation of a statement until the first call to execute is
made. At that point, we have the parameters defined by the calling script, so
we can use the typing specified there when we perform the prepare.

For PDO_PARAM_LOB parameters, we set the binary formatting flag.

We can't just set this flag for all parameters, because its meaning is not
"string data, counted length" but "data is in native format". If this flag is
set for a numeric column and we send the number 1 formatted as a string, then
we will get an "insufficient data left in message" error message, because the
library was expecting sizeof(int4) bytes but only saw 1 byte for "1".

This is infuriating because we have no way to determine the datatypes for
parameters, and the type we explicitly set has to match the type in the
database. The only choice we're left with is telling postgres to deduce the
type; we still have no idea what type was deduced.

show more ...


Revision tags: php-5.1.0, php-4.4.2RC1, RELEASE_0_9_3, php-5.1.0RC6, php-5.1.0RC5, RELEASE_2_0_1, RELEASE_1_0RC2, php-4.4.1, php-5.1.0RC4, RELEASE_0_9_2, RELEASE_0_9_1, php-5.1.0RC3, php-5.1.0RC2, php-4.4.1RC1, RELEASE_0_9_0
# 6cc5e191 24-Sep-2005 Wez Furlong

Refs #34630


Revision tags: RELEASE_1_0RC1
# edc39221 10-Sep-2005 Wez Furlong

if a php bolean makes it as far as the parameter callback, it must really need
to be boolean; express is as native pgsql 't' or 'f'.

Add a test case for Bug #33876, which is a partially

if a php bolean makes it as far as the parameter callback, it must really need
to be boolean; express is as native pgsql 't' or 'f'.

Add a test case for Bug #33876, which is a partially bogus bug.

show more ...


Revision tags: PRE_NEW_OCI8_EXTENSION, php-5.1.0RC2_PRE, php-5.0.5
# 38317bb3 03-Sep-2005 Edin Kadribasic

Don't crash on invalid parameter #34203 (Wez)


Revision tags: php-5.0.5RC2, php-5.0.5RC1, php-5.1.0RC1, BEFORE_UNICODE_MERGE, RELEASE_2_0_0
# 23e671a5 03-Aug-2005 foobar

- Bumber up year


Revision tags: RELEASE_0_9, php-5.1.0b3, php-4.4.0
# 858d8277 09-Jul-2005 Ilia Alshanetsky

Added cursor closer handler.
Fixed memory leak.


# 6ee00c81 08-Jul-2005 Wez Furlong

fix leak


# 6377c0cc 08-Jul-2005 Wez Furlong

Fix PECL #4753


# 512af63a 08-Jul-2005 Wez Furlong

rewrite original names to our preferred format


# 2301d931 08-Jul-2005 Ilia Alshanetsky

Some of us don't have PostgreSQL 8.0 :)


# 529d8177 08-Jul-2005 Wez Furlong

Add early support for native prepared statements in pgsql.
Note that some tests now fail; if we can't resolve this in time for the beta,
the prepare code should be disabled (I'll add a flag f

Add early support for native prepared statements in pgsql.
Note that some tests now fail; if we can't resolve this in time for the beta,
the prepare code should be disabled (I'll add a flag for this later today).

show more ...


# 75cfa5c2 03-Jul-2005 Wez Furlong

probable fix for PECL bug #4546


123456