- 14 Nov, 2014 2 commits
-
-
Arthur Schiwon authored
-
Arthur Schiwon authored
-
- 24 Oct, 2014 1 commit
-
-
Lukas Reschke authored
Otherwise the function is executed n times which is a lot of overhead
-
- 30 May, 2014 1 commit
-
-
Thomas Müller authored
- 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
-
- 13 May, 2014 1 commit
-
-
Robin McCorkell authored
-
- 28 Mar, 2014 1 commit
-
-
Thomas Müller authored
-
- 07 Feb, 2014 1 commit
-
-
Robin Appelman authored
-
- 06 Feb, 2014 1 commit
-
-
Jörn Friedrich Dreyer authored
-
- 16 Jan, 2014 1 commit
-
-
Robin Appelman authored
-
- 21 Dec, 2013 1 commit
-
-
Andreas Fischer authored
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.
-
- 30 Sep, 2013 1 commit
-
-
Thomas Müller authored
Conflicts: lib/private/vcategories.php
-
- 07 Aug, 2013 1 commit
-
-
Bart Visscher authored
-
- 28 Jun, 2013 1 commit
-
-
Bart Visscher authored
-