summaryrefslogtreecommitdiff
path: root/drivers
AgeCommit message (Collapse)AuthorFilesLines
2016-01-02Update version 5.21.0-dev release year to 2016Damien Regad56-56/+56
2016-01-01metaIndexes does not work correctly with upper case table names. see ↵Mark Newnham1-1/+1
https://github.com/ADOdb/ADOdb/issues/176
2015-12-27Merge branch 'hotfix/5.20.2'Damien Regad8-24/+44
2015-12-27Update version to avoid merge conflictsDamien Regad56-56/+56
2015-12-27Reset version to avoid merge conflictsDamien Regad56-56/+56
2015-12-27Bump version to 5.20.2v5.20.2Damien Regad56-56/+56
2015-12-24MetaForeignKeys used deprecated call-by-referenceMark Newnham1-1/+1
2015-12-24Driver now correctly recognizes SQL Server 2014 databases when creating ↵Mark Newnham1-0/+8
sequences
2015-12-20mssql: avoid error when closing RS from destructorDamien Regad2-4/+9
Fix #170
2015-12-20informix: avoid error when closing RS from destructorDamien Regad1-2/+8
Fixing this is somewhat academic considering that informix driver is no longer supported since PHP 5.2.1 Fixes #170
2015-12-20mysqli: Remove use of '@' operator in RS::_close()Damien Regad1-3/+7
Avoids PHP notice when closing recordset Fixes #170
2015-12-20mssql: Remove use of '@' operator in _close()Damien Regad2-2/+6
2015-12-20Whitespace / coding guidelinesDamien Regad2-105/+117
2015-12-20mysqli: Remove use of '@' operator in _close()Damien Regad1-1/+3
2015-12-16Better replacement for preg_replace '/e' flagDamien Regad1-4/+15
Instead of creating an anonymous function, modify the existing _colontrack() function to be used as the callback Fixes #168
2015-12-16Remove useless constructorsDamien Regad41-275/+37
Fixes #171
2015-12-16WhitespaceDamien Regad5-76/+81
2015-12-16PHP7 compatibility: remove preg_replace '/e' flagMarina Glancy1-1/+1
This is the original commit contributed by @marinaglancy (dff32013c1f2f1e51ea8be59d447280d60362e33) minus the changes in mysqlt driver (PHP4 constructor), already fixed in a82f3c692df997e2130cec1e5a0c8f77eb5f1ef8. Fixes #168 Signed-off-by: Damien Regad <dregad@mantisbt.org>
2015-12-16Remove a couple leftover PHP4 constructorsDamien Regad2-10/+0
Follow-up on #139 (commit 9ffa02e6ddc88dbfdfdf4437e0a398cc39960094)A Fixes #168
2015-12-16Remove unused code, add phpDoc blockDamien Regad1-37/+7
2015-12-15mysql: MoveNext() apply field names case conversionDamien Regad2-1/+5
Fixes #167
2015-12-08insert_id did not return correct value after executing stored procedureMark Newnham1-0/+7
2015-12-06Bump version to 5.20.1v5.20.1Damien Regad56-56/+56
2015-11-28Bump version to 5.21devDamien Regad56-56/+56
2015-11-28Bump version to 5.20.0v5.20.0Damien Regad56-56/+56
2015-11-26Adjust header comment blocksDamien Regad56-57/+169
- running SED script - manual adjustments for files not processed by regex
2015-11-14If the last action in a script before shutdown was a call to a meta ↵Mark Newnham1-1/+1
function, the query has already been closed
2015-10-25new public method setConnectionParameter fixes ↵Mark Newnham1-0/+4
https://github.com/ADOdb/ADOdb/pull/158
2015-09-14sqlite3 driver: use -1 for _numOfRowsAsheesh Laroia1-1/+0
This relies on the superclass's built-in default of $this->_numOfRows being set to -1. That causes the sqlite3 driver to rely on ADODB_COUNTRECS. Before this patch, we were setting _numOfRows to positive 1, which meant that any query that checked how many rows were available in a queryset would see literally the number 1, which was not accurate for queries that returned 0 rows or queries that returned more rows. In the case of sqlite3, there appears to be no efficient way to ask the PHP sqlite3 driver how many rows come back from a query, so relying on ADODB_COUNTRECS is the best we can do.
2015-08-14Documentation fixes, warn of deprecation and driver removalMark Newnham1-0/+5
reference issue adodb/adodb/issues/117
2015-08-13Documentation fixesMark Newnham1-1/+5
Documentation fix as requested in ADOdb/ADOdb/issues/117
2015-08-13Documentation fixesMark Newnham1-2/+4
Update to documentation as requested in ADOdb/ADOdb/issues/117
2015-08-13Documentation fixesMark Newnham1-1/+5
Documentation update requested in ADOdb/ADOdb/issues/117
2015-08-12postgres: Noblob optimizationmike.benoit1-1/+1
Saves one query for every connection when blobs arent being used. Fixes #112 Signed-off-by: Damien Regad <dregad@mantisbt.org>
2015-08-11Allow use of prepared statements with driverMark Newnham1-70/+154
Driver failed if a prepared statement was passed to _query(). This was because the _appendN method could only handle an input parameter that was a string . This method now accepts an array as the input parameter
2015-08-11Fix#139: Remove PHP 4 ConstructorsValentin Sheyretski49-276/+151
This is the original commit from @valioz, rebased on latest master Signed-off-by: Damien Regad <dregad@mantisbt.org> Conflicts: drivers/adodb-db2ora.inc.php drivers/adodb-mssqlpo.inc.php drivers/adodb-odbc_oracle.inc.php
2015-08-11Correct function declarations for strict standards. Fixes #142Andrew Nicols21-39/+39
2015-06-28oci8po: prevent replacement of '?' within stringsMark Newnham1-0/+11
When processing an SQL statement containing a '?' character within a string, ADOdb wrongly assumed it is for a bind variable. The number of variables then no longer matches the number passed, and crashes the _query() function. We now identify whether a '?' is within a string and don't use it as a bind variable if so. Fixes #132 Signed-off-by: Damien Regad <dregad@mantisbt.org>
2015-06-25MySQL drivers convert field names caseDamien Regad2-0/+2
With this, the mysql and mysqli (and derived) drivers convert the recordset field names to the case defined by ADODB_ASSOC_CASE. Fixes #100
2015-06-25Move _updatefields() method to ADORecordSetDamien Regad2-63/+0
Currently, this method only exists in postgres7, oci8 and derived drivers. Moving it to the base class will enable reuse by other drivers that need the functionality.
2015-06-25New method ADORecordSet::AssocCaseConvertFunction()Damien Regad1-9/+12
- Avoid code duplication - optimize ADORecordSet_assoc_postgres7::_updatefields()
2015-06-25Coding guidelines and whitespaceDamien Regad3-4/+11
2015-06-25Consistent GetRowAssoc() parameter default valueDamien Regad3-3/+3
MySQL and PostgreSQL used TRUE instead of ADODB_ASSOC_CASE.
2015-06-25Remove useless parameter in GetRowAssoc() callsDamien Regad7-12/+12
Because of the change in default value for the method's parameter, it is no longer needed to specify the constant when calling GetRowAssoc() in the individual drivers.
2015-06-25oci8: driver honors ADODB_ASSOC_CASE when fetching fieldsDamien Regad2-24/+50
This allows use of lowercase field names when executing queries in ADODB_FETCH_ASSOC fetch mode. The _updatefields() method was moved from oci8po to parent oci8 driver. - code was simplified - logic to determine if the operating in associative mode was moved from the callers to the method itself to reduce code duplication. - use of defined ADODB_ASSOC_CASE_* constants Fixes Github #21
2015-06-17PDO: fix broken FetchField functionDamien Regad1-3/+2
Coding guidelines changes actually altered the function's logic by replacing an if/elseif block by a non-equivalent switch statement. Regression introduced by a36f5c4276f7bbf8fc79039a950b0c68d06d2099. Fixes #121, #122
2015-05-21mssqlnative: fix insert_ID() fails if server returns more than 1 rowgitjti1-3/+4
If inserting involves trigger action, SQL server probably returns more than result ”rows” and we are interested in last one only. Fixes #41, PR #102 Signed-off-by: Damien Regad <dregad@mantisbt.org>
2015-05-21mssqlnative: use correct setting 'WarningsReturnAsErrors'Ray Morris1-2/+2
The driver called sqlsrv_configure('warnings_return_as_errors', 0), which throws "error code = -14, sqlsrv_configure: message = An invalid parameter was passed to sqlsrv_configure". The proper setting is 'WarningsReturnAsErrors', as per documentation http://php.net/manual/en/function.sqlsrv-configure.php Fixes #103 Signed-off-by: Damien Regad <dregad@mantisbt.org> Referenced the fix in the changelog
2015-05-15sqlite3: Fix result-less SQL statements executed twiceDamien Regad2-2/+12
The sqlite3 driver relies on SQLite3::query to execute the statement, which returns an empty SQLite3Result while the ADOConnection::_Execute() method expects true for handling of result-less queries. This causes the query to be executed a second time when ADOdb initializes the recordset for what it wrongly assumes to be a SELECT statement. This also addresses the same behavior with the sqlite driver, but the fix was not tested as I don't have a sqlite 2 setup available. Fixes #99
2015-05-15MSSQL: fix fail on insert when statement contains ';'stekule1-1/+1
In mssql a tick mark (') in a value string is escaped via a second one. Therefore the number of tick marks before the semicolon must be odd (since the string starts with a tick mark). Semicolons should be allowed after an odd number of tick marks. There must be a character between the odd tick mark groups. Fixes #97, see also #96
generated by cgit v1.3 (git 2.53.0) at 2026-07-08 22:48:30 +0000