Skip to content

Releases: pacman82/odbc-api

odbc-api-v11.1.1

19 Feb 21:58
Compare
Choose a tag to compare

Fixed

  • Return type of decimal_text_to_i32 is now indeed i32 and no longer i64

odbc-api-v11.1.0

19 Feb 21:44
Compare
Choose a tag to compare

Added

  • Add conversion functions decimal_text_to_i64, decimal_text_to_i32

Other

  • (deps) bump tempfile from 3.17.0 to 3.17.1
  • (deps) bump tempfile from 3.16.0 to 3.17.0

odbc-api-v11.0.0

16 Feb 12:47
Compare
Choose a tag to compare

Added

  • [breaking] Query timeout for into_cursor
  • [breaking] Introduce query timeout to Connection::execute
  • Add Connection::into_preallocated

Other

  • Add missing timeout parameter to failing tests
  • [breaking] PreallocatedPolling is generic over handle type
  • All but into_polling of Preallocateds implementation is now generic over statment handle
  • [breaking] Preallocated is now dependend on statement handle type, rather than lifetime
  • More usecase centric documentation for set_query_timeout_sec

odbc-api-derive-v10.0.0

16 Feb 12:47
Compare
Choose a tag to compare
chore: release

odbc-api-v10.2.0

15 Feb 11:40
Compare
Choose a tag to compare

Added

  • Support for query timeouts. Preallocated::set_query_timeout_sec and Prepared::set_query_timeout_sec can be used to trigger a timeout error, if the first data from that statement exceeds the time limit. This requires driver support.

Other

  • query timeout
  • (deps) bump winit from 0.30.8 to 0.30.9
  • (deps) bump tempfile from 3.15.0 to 3.16.0
  • (deps) bump log from 0.4.22 to 0.4.25
  • (deps) bump thiserror from 2.0.10 to 2.0.11
  • (deps) bump tokio from 1.42.0 to 1.43.0
  • (deps) bump thiserror from 2.0.9 to 2.0.10
  • (deps) bump winit from 0.30.7 to 0.30.8
  • (deps) bump tempfile from 3.14.0 to 3.15.0
  • (deps) bump syn from 2.0.96 to 2.0.98
  • (deps) bump syn from 2.0.95 to 2.0.96
  • (deps) bump syn from 2.0.94 to 2.0.95

odbc-api-derive-v9.0.3

15 Feb 11:40
Compare
Choose a tag to compare
chore: Update changelog and version number

odbc-api-v10.1.1

03 Jan 12:50
Compare
Choose a tag to compare

Other

  • Improve panic message on invalid indicator values

odbc-api-v10.1.0

02 Jan 19:49
Compare
Choose a tag to compare

Added

  • autodetect homebrew library path during build

Other

  • (deps) bump thiserror from 2.0.8 to 2.0.9
  • (deps) bump anyhow from 1.0.94 to 1.0.95
  • (deps) bump winit from 0.30.5 to 0.30.7
  • (deps) bump env_logger from 0.11.5 to 0.11.6
  • (deps) bump thiserror from 2.0.7 to 2.0.8
  • (deps) bump thiserror from 2.0.6 to 2.0.7
  • (deps) bump thiserror from 2.0.4 to 2.0.6
  • (deps) bump thiserror from 2.0.3 to 2.0.4
  • (deps) bump anyhow from 1.0.93 to 1.0.94
  • (deps) bump tokio from 1.41.1 to 1.42.0
  • (deps) bump syn from 2.0.93 to 2.0.94
  • (deps) bump syn from 2.0.92 to 2.0.93
  • (deps) bump syn from 2.0.91 to 2.0.92
  • (deps) bump quote from 1.0.37 to 1.0.38
  • (deps) bump syn from 2.0.90 to 2.0.91
  • (deps) bump syn from 2.0.89 to 2.0.90

odbc-api-derive-v9.0.2

02 Jan 19:49
Compare
Choose a tag to compare
chore: Clean up Changelog

odbc-api-v10.0.0

24 Nov 21:24
Compare
Choose a tag to compare

Added

  • [breaking] odbc-api will now use narrow function calls by default on non-windows systems. This assumes that the ODBC driver on that platform uses UTF-8 encoding. This is usually the case as many Linux systems use an UTF-8 locale. Outside of windows the wide function calls are usually less battle tested on drivers. Downstream artefacts like arrow-odbc and odbc2parquet therefore have been compiling with the narrow flag on non-windows systems for quite a while now to opt into the behavior which most likely works by default. However if somebody had a non-windows platform with a non-utf 8 local and a driver which actually could use UTF-16, he could not set appropriate compiler flags to revert the narrow feature added by these crates. Since the default behavior for each platform is now triggered by odbc-api itself, downstream artefacts can overwrite it both ways. E.g. using the narrow flag on windows to get some speed, if they know their target platform has a UTF-8 local configured. Or the other way around using the wide flag on a Linux system to e.g. handle special character in column names, which only seem to work with the wide variants of the drivers. So if you used odbc-api previously on Linux without any flags it did by default use the wide function calls. It now uses the narrow ones by default. If you want the old behavior just specify the wide feature flag. For windows users nothing breaks.

Other

  • (deps) bump thiserror from 2.0.0 to 2.0.3
  • (deps) bump csv from 1.3.0 to 1.3.1
  • (deps) bump tempfile from 3.13.0 to 3.14.0
  • (deps) bump tokio from 1.41.0 to 1.41.1
  • (deps) bump thiserror from 1.0.68 to 2.0.0
  • (deps) bump anyhow from 1.0.92 to 1.0.93
  • (deps) bump thiserror from 1.0.66 to 1.0.68
  • (deps) bump thiserror from 1.0.65 to 1.0.66
  • (deps) bump anyhow from 1.0.91 to 1.0.92
  • (deps) bump syn from 2.0.87 to 2.0.89
  • (deps) bump syn from 2.0.86 to 2.0.87
  • (deps) bump syn from 2.0.85 to 2.0.86