1. 02 Jan, 2014 2 commits
  2. 01 Jan, 2014 6 commits
  3. 31 Dec, 2013 1 commit
  4. 30 Dec, 2013 1 commit
  5. 29 Dec, 2013 1 commit
  6. 28 Dec, 2013 1 commit
  7. 27 Dec, 2013 1 commit
  8. 26 Dec, 2013 1 commit
  9. 25 Dec, 2013 1 commit
  10. 24 Dec, 2013 5 commits
  11. 23 Dec, 2013 1 commit
  12. 22 Dec, 2013 3 commits
  13. 21 Dec, 2013 3 commits
    • Andreas Fischer's avatar
      Remove all uses of numRows(). · 4bc2a223
      Andreas Fischer authored
      4bc2a223
    • Andreas Fischer's avatar
      Remove OC_DB_StatementWrapper::numRows(). · 63a2bea7
      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.
      63a2bea7
    • Jenkins for ownCloud's avatar
      [tx-robot] updated from transifex · cd26631a
      Jenkins for ownCloud authored
      cd26631a
  14. 20 Dec, 2013 3 commits
  15. 19 Dec, 2013 10 commits