| Age | Commit message (Collapse) | Author | Files | Lines |
|
$where was wrongly typed as bool. Changed it to string and updated
the default value from false to ''.
Fixes #915
|
|
Executing a schema update that adds a column more than once will
generate a column already exists error.
This prevents the error by appending `IF NOT EXISTS` to the generated
SQL on PostgreSQL 9.6 or later.
Fixes #897
Signed-off-by: Damien Regad <dregad@mantisbt.org>
Reworded commit message
|
|
|
|
Ensures that the recordset is returned in the default provided by the
PHP driver as per the documentation.
Fixes #886
|
|
|
|
|
|
ADOConnection's errorNo() and errorMsg() methods were returning 0 / ''
when executing an SQL statement with bound parameters, since the
introduction of true prepared statements (in #655).
This is because they are getting error information from the mysqli
connection object, but when using prepared statements, it must be
retrieved from the mysqli_stmt object.
Fixes #872
|
|
|
|
If called incorrectly, the affected_rows() method now returns false
instead of returning an error from the SQL server driver.
Fixes #895
|
|
|
|
adodb_strip_order_by() should only remove the ORDER BY clause from the
outer SELECT statement, not from subqueries.
Fixes #870
|
|
|
|
|
|
The replacement of preg_match() by preg_match_all() in commit
8eaf842d19e4206e1c44e0eda44688ebfa1728ed basically made most of the
code in the function useless (the block parsing the SQL statement for
paretheses was never called).
Also, the logic to retrieve the last ORDER BY clause was a bit
contrived.
Fixes #869
|
|
Partial revert of 721c31492ac77aa1bd9bdd01193cd6071087b49f.
This was an early attempt to fix #848; the actual fix was implemented in
the PostgreSQL driver, but the change to ADORecordSet::__destruct() was
not reverted.
Fixes #867
|
|
|
|
https://github.com/ADOdb/ADOdb/issues/124#issuecomment-1238798400
|
|
|
|
|
|
alterTableSql() uses core methods instead of driver-specific ones.
Change method used to create SQL statements.
Fixes #865, #383
Signed-off-by: Damien Regad <dregad@mantisbt.org>
|
|
|
|
On PHP 8.x, executing an update query with the Firebird or Interbase
driver results in a Fatal error: Uncaught TypeError: ibase_num_fields():
Argument #1 ($query_result) must be of type resource, int given.
Problem is caused by fbird_query() / ibase_query() returning the number
of affected rows instead when executing INSERT, UPDATE and DELETE
statements, but ADOConnection::_Execute() expects true.
This was already triggering a warning in earlier PHP versions, but it
was silenced by the @ operator.
Fixes #858
|
|
ValueError: str_repeat(): Argument #2 ($times) must be greater than or
equal to 0 on adodb/adodb-lib.inc.php:1255
Merge PR #856, fixes #852
|
|
|
|
|
|
See https://github.com/ADOdb/ADOdb/pull/856#discussion_r953591183
|
|
|
|
|
|
|
|
|
|
|
|
This fix eliminates the error in str_repeat when the number of repeats hits zero In addition, the function is refactored with improved variable names and docblocks
|
|
|
|
|
|
Fixes #862
|
|
|
|
|
|
Fixes #848
|
|
Replace hardcoded '-1' value when creating dummy RecordSets.
Issue #848
|
|
Insert_id() attempts to force the return value to an integer data type
which fails if the value is out of range.
Fixes #853
|
|
|
|
Merge PR https://github.com/ADOdb/ADOdb/pull/843
|
|
|
|
If errorMsg() is called after closing the MySQL connection (with
mysqli_close()), the method will throw a PHP warning:
Uncaught Error: mysqli object is already closed.
With PHP < 8.0 the warning won't be thrown due to the @ operator, but
the function will return false; with PHP 8.0 or later, this is a fatal
error (exception).
Remove unnecessary @ operator.
Fixes #842
|
|
MySQL 8 returns an object even if the client connection fails. This
causes ADOConnection_mysqli::errorMsg(), which expects the connection
object to be empty if there is no connection, to throw an error.
Fixes #842
|
|
|
|
|
|
|
|
|
|
|