1. 28 Sep, 2018 1 commit
  2. 15 Aug, 2018 1 commit
  3. 14 Aug, 2018 1 commit
  4. 15 May, 2018 6 commits
  5. 02 May, 2018 1 commit
  6. 22 Apr, 2018 1 commit
  7. 10 Apr, 2018 1 commit
  8. 25 Mar, 2018 1 commit
  9. 23 Mar, 2018 2 commits
    • Roman S. Borschel's avatar
      Row type must read all columns as a MaybeColumn · b08f750d
      Roman S. Borschel authored
      The 'Row' type must be able to represent any result row and all columns
      are "nullable" in Cassandra. Concretely, it is used as the result type
      of lightweight transactions in cql-io, which return the full row on a
      failed (i.e. conflicting) insert as well as the conflicting values on a
      failed update, both of which may contain null values. This problem
      showed up on testing the failure cases of lightweight transactions in
      cql-io.
      b08f750d
    • Roman S. Borschel's avatar
      Bound size of generated Value trees in tests. · 400e66f4
      Roman S. Borschel authored
      To ensure termination and limit CPU and memory usage.
      400e66f4
  10. 20 Mar, 2018 4 commits
  11. 01 Feb, 2018 4 commits
  12. 21 May, 2017 1 commit
  13. 07 May, 2017 1 commit
  14. 29 Mar, 2017 1 commit
  15. 28 Mar, 2017 1 commit
  16. 21 Mar, 2017 1 commit
  17. 26 Dec, 2016 2 commits
  18. 20 Dec, 2016 1 commit
  19. 18 Sep, 2016 1 commit
  20. 10 Sep, 2016 1 commit
  21. 17 Jun, 2016 3 commits
    • Toralf Wittner's avatar
      Update CHANGELOG · daf87ea9
      Toralf Wittner authored
      daf87ea9
    • Toralf Wittner's avatar
      Fix Tests. · 10129c1c
      Toralf Wittner authored
      10129c1c
    • Toralf Wittner's avatar
      Merge branch 'udt-tuple-tweaks' into 'develop' · a9343340
      Toralf Wittner authored
      Tweak UDT and tuple handling.
      
      This merge request contains a few suggestions to the handling of UDT and tuple columns:
      
        * Remove the "keyspace" from the `UdtColumn` constructor. It makes it
          impossible to use a configurable keyspace in an application together with UDTs since
          the keyspace cannot be provided in the implementation of the `ctype`
          typeclass method in such a scenario. Furthermore, UDTs are
          constrained to the keyspace they are defined in [1], so that
          comparing keyspace names during the "typechecking" of a response to a request that is itself confined to a single keyspace
          does not seem to add much value.
      
        * Adjust the typechecking of UDT columns in responses to include the
          type name as well as the field names and their types.
      
        * Adjust the typechecking of tuple columns in responses to use a
          proper recursive type equality check over the components (e.g. the current typecheck
          for tuples produces spurious errors on `varchar` vs `text`).
      
      Thereby I removed the `encodeColumnType` function since column types are
      never encoded by CQL clients according to the protocol.
      
      [1] https://issues.apache.org/jira/browse/CASSANDRA-6643
      
      See merge request !2
      a9343340
  22. 16 Jun, 2016 1 commit
    • Roman S. Borschel's avatar
      Tweak UDT and tuple handling. · c9702dfe
      Roman S. Borschel authored
        * Remove the "keyspace" from the UdtColumn constructor. It makes it
          impossible to use a configurable keyspace in an application since
          the keyspace cannot be provided in the implementation of the 'ctype'
          typeclass method in such a scenario. Furthermore, UDTs are
          constrained to the keyspace they are defined in [1], so that
          comparing keyspace names during the "typechecking" of response
          processing does not seem to add much value.
      
        * Adjust the typechecking of UDT columns in responses to include the
          type name as well as the field names and types.
      
        * Adjust the typechecking of tuple columns in responses to use a
          proper recursive type equality check (e.g. the current typecheck
          for tuples produces spurious errors on 'varchar' vs 'text').
      
      Thereby remove the 'encodeColumnType' function since column types are
      never encoded by CQL clients according to the protocol.
      
      [1] https://issues.apache.org/jira/browse/CASSANDRA-6643Signed-off-by: Roman S. Borschel's avatarRoman S. Borschel <roman@pkaboo.org>
      c9702dfe
  23. 15 Jun, 2016 3 commits