1. 14 Sep, 2017 10 commits
  2. 13 Sep, 2017 2 commits
  3. 12 Sep, 2017 4 commits
  4. 10 Sep, 2017 3 commits
  5. 03 Sep, 2017 4 commits
  6. 01 Sep, 2017 1 commit
  7. 22 Aug, 2017 4 commits
  8. 06 Aug, 2017 2 commits
  9. 31 Jul, 2017 1 commit
  10. 30 Jul, 2017 1 commit
  11. 25 Jul, 2017 3 commits
  12. 21 Jul, 2017 5 commits
    • Vadim Zeitlin's avatar
      Merge branch 'odbc-string-len' · 7a6559c1
      Vadim Zeitlin authored
      Fix handling of strings in bulk operations in ODBC and DB2 backends and
      get_affected_rows() behaviour in ODBC.
      Closes #561, also see #202, #495.
    • Vadim Zeitlin's avatar
      Add test checking string length when using bulk insert · c6aef12b
      Vadim Zeitlin authored
      This used to be broken, so add a test to check that it works after the
      changes of the last commit and to avoid breaking it again.
    • Vadim Zeitlin's avatar
      Fix the length of strings in DB2 vector operations · 51c4c1e1
      Vadim Zeitlin authored
      This is the same as a2c1ce7aceb564c11f48b3b586e2e77245c3deab except for
      DB2 backend (which is, of course, very similar to ODBC one as ODBC API
      is very close to DB2 CLI).
    • Vadim Zeitlin's avatar
      Fix the length of strings in ODBC vector operations · be4f26fe
      Vadim Zeitlin authored
      Saving a string of length N in the database saved it as a string of
      length N+1 with a trailing NUL explicitly written into the database and
      reading it back resulted in a string of length N+1 too, i.e. it didn't
      survive the round trip (notice that this bug only affected vector
      operations, scalar ones worked correctly).
      Fix this by not writing the trailing NUL in odbc_vector_use_type_backend
      and fix the strings returned from odbc_vector_into_type_backend by not
      assuming that they're NUL-terminated any more: in fact, they can be, but
      they also can be right-padded with spaces, which need to be removed.
      Notice that this does mean that we still have a problem with
      inconsistent behaviour for the strings with the trailing spaces between
      ODBC backend and others: ODBC one will strip them from the returned
      strings, but other backends will not. It is not clear what can be done
      about it, unfortunately.
    • Vadim Zeitlin's avatar
      Improve get_affected_rows() documentation · 521a8408
      Vadim Zeitlin authored
      Mention that the exact result of this method can't be relied upon for
      the partially successful statements when using ODBC: some drivers
      (including the widely used MS SQL native client) simply don't return
      this information at all, while others (MySQL) just return wrong number
      of rows.
      Also remove the apparently obsolete note about this method not supported
      in the Oracle backend as it does seem to implement it.