| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | |
| | |
| | |
| | |
| | |
| | | |
And remove unnecessary try-catch.
Closes GH-6505.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #72368
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Generate a param count mismatch error even if the query contains
no placeholders.
Additionally we shouldn't HANDLE errors from pdo_parse_params,
which are always reported via raise_impl_error. Doing so results
in duplicate error messages.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #79131
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When a driver reports an error during EVT_ALLOC (and some over EVTs),
make sure we handle it as usual, i.e. warn or throw.
This requires some adjustments in PDO PgSQL to stop manually doing
this through an impl error.
Unfortunately the PDO PgSQL error messages regress because of this,
as they now include a completely arbitrary error code. There doesn't
seem to be an ability to skip it right now.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #79872 by improving error message
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The actual behavior here is correct, but the previous error
message was misleading, as neither fetchAll() nor buffered queries
would help in this situation. Instead it is necessary to consume
all rowsets, which can be done by either unsetting the statement
or calling closeCursor().
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #76815
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #76815
|
| | |
| | |
| | |
| | |
| | |
| | | |
When we receive an error while reading a result set, we should
assume that no more result sets are available. libmysqlclient
implements the same behavior.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #71145
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #71145
|
| | |
| | |
| | |
| | | |
Consume any additional result sets when running INIT_COMMAND.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Given the number of duplicates this bug report had, it seems
worthwhile to fix this on PHP-7.4 as well.
Cherry-pick of 106e7e4bca7c0fd975eb219b18e3c34957ba8657.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #70066
|
| | |
| | |
| | |
| | |
| | | |
If we fall back to emulated prepared statements, destroy S->stmt,
so the code doesn't get confused about which mode we're in.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #66878
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Keep track of whether we have fully consumed all result sets,
either using nextRowset() calls or closeCursor() and skip the
attempt to consume remaining results sets during destruction in
that case.
Especiall if closeCursor() has been used, we really shouldn't
have this sort of cross-statement inference.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | | |
* PHP-8.0:
Remove unnecessary more_results() checks
Add ifdef for mysqlnd only function
|
| | |
| | |
| | |
| | | |
Just calling next_result() is sufficient.
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | | |
* PHP-8.0:
PDO MySQL: Extract common code for handling PS results
PDO MySQL: Use set_row_count() helper
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
PDO MySQL: Make sure nextRowset() works with partially consumed result
|
| | |
| | |
| | |
| | |
| | |
| | | |
This was already working in all cases apart from native prepared
statements with unbuffered queries. In that case invoking
stmt_free_result() addresses the issue.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
PDO MySQL: Handle error during closeCursor()
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #78154
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #78154
|
| | |
| | |
| | |
| | | |
Handle errors during next_result in exec.
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | | |
* PHP-8.0:
Fix stmt_free_result implementation and usage
Make XFAILED test less broken
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Two bugs both affecting the bug_pecl_7976.phpt test ("works with
mysqlnd" haha):
* We should not change the connection state in stmt_free_result.
This makes mysql_stmt_free_result usable under mysqlnd and
not just libmysqlclient.
* If we call mysql_stmt_free_result, we still need to consume
any outstanding result sets.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Handle changing column count in mysqlnd result binding
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If the count changes from prepare to execute and result_bind is
alreadly allocated, reallocate it there.
This is something of a hack. It would be cleaner to require that
result bindings are registered only after execute, when the final
result set fields are known. But mysqli at least directly exposes
this to the user, so we have no guarantee.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
PDO MySQL: Normalize handling of empty stored procedure result set
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
MySQL always returns a trailing empty result set for stored
procedure calls, which is used to convey status information.
The PDO MySQL implementation is presently confused about what to
do with it: If mysqlnd is used and native prepared statements are
used, this result set is skipped. In all other cases it is not
skipped. We also have quite a few XFAILed tests relating to this.
This patch normalizes (for PHP-8.0 only) the behavior towards
always retaining the empty result set. This is simply how MySQL
stored procedures work (some expletives omitted here) and we can't
distinguish this "useless" result set from an empty result of a
multi query. Multi queries are not a concern for native prepared
statements, as PDO does not allow them in that case, but they are
a concern for emulated prepared statements.
Closes GH-6497.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Handle column count change in PDO MySQL
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This has been fixed for PDO SQlite by GH-4313, however the same
issue also applied to PDO MySQL.
Move the column count setting function into the main PDO layer
(and export it) and then use it in both PDO SQLite and PDO MySQL.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Enable XFAILed test
|
| | |
| | |
| | |
| | |
| | | |
This one had a rather scary XFAIL message, but seems to work just
fine...
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #63185
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #63185
|
| | | |
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fixed bug #80458
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fixed bug #80458
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If there is no result set (e.g. for upsert queries), still allow
fetching to occur without error, i.e. treat it the same way as
an empty result set.
This normalizes behavior between native and emulated prepared
statements and addresses a regression in PHP 7.4.13.
|
|\ \ \
| |/ /
| | |
| | |
| | | |
* PHP-8.0:
Fix #80312: change default engine from MyISAM to InnoDB in tests
|
| |\ \
| | |/
| | |
| | |
| | | |
* PHP-7.4:
Fix #80312: change default engine from MyISAM to InnoDB in tests
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Change mysqli and pdo_mysql tests configuration to use by default
InnoDB instead of MyISAM.
Closes GH-6405.
|