| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Substring() is not required for the core functionality and this allows us to get rid of a huge hack...
|
| | |
|
| | |
|
| |
|
|
| |
Otherwise the function is executed n times which is a lot of overhead
|
| |
|
|
|
|
|
| |
- kill replaceDB() - this function is unused and it's implementation obviously wrong
- add method annotation OC_DB_StatementWrapper::fetchAll
- remove duplicate code in Test_DBSchema and reuse OC_DB::tableExists
- remove unused variables
|
| | |
|
| |
|
|
| |
wrapped statement object
|
| |\
| |
| |
| |
| | |
Conflicts:
lib/private/migration/content.php
|
| | |\
| | |
| | | |
Add bindParam to the database statement wrapper
|
| | | | |
|
| |\| |
| | |
| | |
| | |
| | | |
Conflicts:
lib/private/appconfig.php
|
| | |/ |
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using this method will result in an unneccesary extra SQL query (which also may
return an incorrect result because the underlying table changed in the
meantime).
In general:
If you are performing an UPDATE, DELETE or equivalent query,
OC_DB_StatementWrapper::execute() will already give you the number of
"affected rows" via \Doctrine\DBAL\Driver\Statement::rowCount(). This will
not work for SELECT queries, however.
If you want to know whether a table contains any rows matching your condition,
use "SELECT id FROM ... WHERE ... LIMIT 1".
If you want to know whether a table contains any rows matching your condition
and you also need the data, use "SELECT ... FROM ... WHERE ...", then use
one of the fetch() methods.
If you want to count the number of rows matching your condition, use use
"SELECT COUNT(...) AS number_of_rows FROM ... WHERE ...", then use one of the
fetch() methods.
|
|
|
Conflicts:
lib/private/vcategories.php
|
