v0.5.0
Added
Collation-Aware VARCHAR Decoding
- New
encodingfeature for proper decoding of VARCHAR columns with non-UTF-8 collations Collation::encoding()method returns theencoding_rs::Encodingfor a collation's LCIDCollation::encoding_name()method returns human-readable encoding nameColumn.collationfield exposes collation metadata for string columnsColumn.encoding_name()convenience method (requiresencodingfeature)- Support for Windows code pages: 1252 (Latin1), 1251 (Cyrillic), 1250 (Central European),
932 (Shift_JIS), 936 (GB18030), 949 (Korean), 950 (Big5), and more - Example:
collation_encoding.rsdemonstrating collation-aware decoding
Changed
- BREAKING:
Columnstruct marked#[non_exhaustive]- Use
Column::new()or builder methods to construct instances - Allows future field additions without breaking changes
- Use
Fixed
- VARCHAR columns with non-UTF-8 collations (e.g.,
SQL_Latin1_General_CP1_CI_AS) now decode correctly - Previously, characters like "Café" would display as "Caf�" when using Windows-1252 encoding
What's Changed
- deps: bump proc-macro2 from 1.0.103 to 1.0.104 by @dependabot[bot] in #14
- deps: bump serde_json from 1.0.147 to 1.0.148 by @dependabot[bot] in #15
- deps: bump windows from 0.59.0 to 0.62.2 by @dependabot[bot] in #16
- feat(protocol): add collation-aware VARCHAR decoding by @jkindrix in #23
Full Changelog: v0.4.0...v0.5.0