CQLAI v0.1.3

Fix CLI option bugs, add cqlsh compatibility flags, and improve docs …

CQLAI v0.1.2rc1

Support for rc? versioning to test builds

v0.1.2

Replace fpm with pkgbuild (#71)

CQLAI v0.1.1

What's Changed

• Fixed Issue 63 by @hshimizu in #64

Full Changelog: v0.1.0...v0.1.1

v0.1.0

Removing files

CQLAI v0.0.31

feat: Add vector string parsing and fix SET import from Parquet

Vector Export:
- Added parseVectorString() to handle vector data when gocql returns it as
  string format (e.g., "[0.12 0.45 0.78]") instead of []float32
- Parses space-separated float values and converts to proper float32/float64
  based on Arrow list element type
- Vectors are correctly stored as Arrow LIST<FLOAT32> in Parquet

SET Import Fix:
- Fixed COPY FROM Parquet failing on SET<TEXT> columns with "Unexpected
  receiver type" error
- Added SET type detection for "tags" column name (common pattern)
- Updated formatListValue() to use curly braces {...} for sets instead of
  square brackets [...]
- Sets now correctly formatted as CQL set syntax during import

Both LIST and SET collections now properly round-trip through Parquet export
and import.

v0.0.30

fix: Tab completion issues with keyword duplication and INSERT column…

CQLAI v0.0.29

feat: Add support for legacy Common Name certificate verification

Modern Go TLS (1.15+) requires certificates to use Subject Alternative Names
(SANs) and rejects certificates that only have Common Name (CN) fields.
This causes connection failures with older Cassandra certificates.

This commit adds an AllowLegacyCN configuration option that:
- Bypasses standard TLS verification when enabled
- Manually verifies the certificate chain is signed by trusted CA
- Manually verifies the CN matches the expected hostname
- Falls back to standard SAN verification if available

Security is maintained through manual certificate chain and hostname
verification in the VerifyConnection callback. This provides the same
security guarantees as SAN-based verification.

For cqlshrc compatibility, AllowLegacyCN is automatically enabled when
validate=true is set, matching cqlsh behavior with legacy certificates.

CQLAI v0.0.28

fix: Set TLS ServerName for hostname verification when using SSL

When connecting to Cassandra with SSL enabled, gocql resolves the hostname
to an IP address. This causes TLS verification to fail if the certificate
only contains the hostname (not the IP) in the Subject Alternative Name (SAN).

The fix sets tlsConfig.ServerName to the original hostname, which tells Go's
TLS client to verify the certificate against the hostname even when the
actual connection is made to the resolved IP address.

This makes cqlai behave consistently with cqlsh when using hostname-based
certificates with validate=true in cqlshrc.

CQLAI v0.0.27

Merge pull request #61 from axonops/2025-10-22-bugfixes

fix: Display results when CAPTURE is active