| #
916673a3 |
| 02-Dec-2006 |
Ilia Alshanetsky |
Fixed bug #39527 (Failure to retrieve results when multiple unbuffered,
prepared statements are used in pdo_mysql).
|
|
Revision tags: php-5.2.0, php-5.2.0RC6, php-5.2.0RC5, 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, php-4.4.3, php-5.2.0RC1, php-4.4.3RC2, BEFORE_NEW_OUTPUT_API, php-4.4.3RC1, php-5.1.4, RELEASE_1_0_3, php-5.1.3, php-5.1.2, RELEASE_1_3 |
|
| #
64de59d9 |
| 22-Apr-2006 |
Wez Furlong |
avoid unterminated loop when closing the statement.
|
|
Revision tags: php-5.1.3RC3 |
|
| #
bb5f3aa0 |
| 09-Apr-2006 |
Wez Furlong |
This completes the fix for PECL #5827; we need to gobble up result sets in the
stmt dtor too.
|
| #
0f4137fb |
| 09-Apr-2006 |
Wez Furlong |
fix for PECL Bug #5827.
We're responsible for gobbling up supplemental result sets in closeCursor()
(which is what PDO does for us if we didn't implement our own closer routine).
|
|
Revision tags: php-5.1.3RC2, php-5.1.3RC1, RELEASE_1_2 |
|
| #
3608dd4c |
| 14-Feb-2006 |
Ilia Alshanetsky |
Fixed bug #36345 (PDO/MySQL problem loading BLOB over 1MB).
|
|
Revision tags: 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, RELEASE_1_1_1, RELEASE_1_1, RELEASE_1_0 |
|
| #
012e5bf4 |
| 05-Dec-2005 |
Antony Dovgal |
add NEWDECIMAL, NEWDATE, GEOMETRY, SET and ENUM field types
|
|
Revision tags: RELEASE_2_0_2 |
|
| #
22efcfd5 |
| 30-Nov-2005 |
Antony Dovgal |
MFH: fix possible crash in pdo_mysql_stmt_dtor()
|
|
Revision tags: php-5.1.1, 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 |
|
| #
c28a9a4e |
| 29-Oct-2005 |
Wez Furlong |
Closes PECL Bug #5802
|
| #
b2424b2e |
| 29-Oct-2005 |
Wez Furlong |
argh! we don't want to NULL the stmt here; freeing the results is not the same
as destroying the prepared statement handler, so we're leaking and breaking, as
can be seen by running the test
argh! we don't want to NULL the stmt here; freeing the results is not the same
as destroying the prepared statement handler, so we're leaking and breaking, as
can be seen by running the test suite.
brown paper bag for PDO in PHP 5.1RC4?
show more ...
|
|
Revision tags: php-5.1.0RC4 |
|
| #
7c01510b |
| 27-Oct-2005 |
Antony Dovgal |
MFH: free && set to NULL S->stmt
|
|
Revision tags: RELEASE_0_9_2, RELEASE_0_9_1 |
|
| #
4d0439e4 |
| 19-Oct-2005 |
Ilia Alshanetsky |
MFH: Fixed bug #34623 (Crash in pdo_mysql on longtext fields).
|
|
Revision tags: php-5.1.0RC3, php-5.1.0RC2, php-4.4.1RC1, RELEASE_0_9_0 |
|
| #
b47525e5 |
| 29-Sep-2005 |
Marcus Boerger |
- TSRM fix
|
| #
fdd42afa |
| 25-Sep-2005 |
Wez Furlong |
Fixup LOB handling for inserts (refs #34630).
Also tripped over the return of PECL #5200; looks like mysql doesn't return an
accurate length for the columns. The PDO driver will sanity
Fixup LOB handling for inserts (refs #34630).
Also tripped over the return of PECL #5200; looks like mysql doesn't return an
accurate length for the columns. The PDO driver will sanity check the real
length against the buffer size it allocated (based on the info provided by
mysql), so that we won't overrun the buffer. In addition, if a varchar field
is reported as having a length of less than 128, we'll allocate 128 just in
case.
If the data is truncated, report it via the appropriate sqlstate code.
There must be a better way to do this stuff.
show more ...
|
|
Revision tags: RELEASE_1_0RC1, PRE_NEW_OCI8_EXTENSION, php-5.1.0RC2_PRE, php-5.0.5 |
|
| #
156a899e |
| 01-Sep-2005 |
Ilia Alshanetsky |
MFH: Fixed bug #34001 (pdo_mysql truncates numberic fields at 4 chars)
|
|
Revision tags: php-5.0.5RC2, php-5.0.5RC1, php-5.1.0RC1, BEFORE_UNICODE_MERGE, RELEASE_2_0_0, RELEASE_0_9 |
|
| #
99d8090c |
| 20-Jul-2005 |
Ilia Alshanetsky |
Fixed memory corruption (wrong order of operations of stored prep. stmt).
Optimize the max length calculation process.
|
| #
97e8c6f4 |
| 20-Jul-2005 |
Ilia Alshanetsky |
Proper handling for databases that need to pre-calculate length of large
columns, which is not normally done for performance reasons.
|
| #
9438584d |
| 20-Jul-2005 |
Ilia Alshanetsky |
Only set attribute if result set contains some columns.
|
| #
1e1d2e2b |
| 20-Jul-2005 |
Ilia Alshanetsky |
clean up
|
| #
8adbc92d |
| 20-Jul-2005 |
Wez Furlong |
this hack can and does segv; let's remove it.
|
|
Revision tags: php-5.1.0b3 |
|
| #
fc48f909 |
| 14-Jul-2005 |
Wez Furlong |
gah!
|
| #
0601249f |
| 14-Jul-2005 |
Wez Furlong |
it is not an error for a statement to return 0 rows.
Andrey: please run the test suite before each commit!
This broke beta 3 and was clearly visible as a result of running the tests.
it is not an error for a statement to return 0 rows.
Andrey: please run the test suite before each commit!
This broke beta 3 and was clearly visible as a result of running the tests.
Running further tests now.
show more ...
|
| #
8899425e |
| 12-Jul-2005 |
Andrey Hristov |
strictly check the result of mysql_affected_rows()
|
|
Revision tags: php-4.4.0 |
|
| #
31de8e90 |
| 10-Jul-2005 |
Andrey Hristov |
stmt->column_count is set only if the result has been already bound, don't
rely on that and use the real count which is kept in st_mysql_stmt
#of course using internal values is bad idea but
stmt->column_count is set only if the result has been already bound, don't
rely on that and use the real count which is kept in st_mysql_stmt
#of course using internal values is bad idea but the comment already says
#that this should be fixed
show more ...
|
| #
55ab9b75 |
| 10-Jul-2005 |
Andrey Hristov |
ok, calculate max_length only in case of a blob (normal, medium, long).
in case of a varchar lets allocate 255 bytes and be quick without asking
libmysql to update max_length
|
