Skip to content

FlyQL

vgolang/v1.0.1 Bugfix

This release fixes issues for SREs watching stability and regressions.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

ast clickhouse code-generator flyql go javascript
+6 more
parser postgresql query-language sql starrocks vue

Summary

AI summary

Fixed PostgreSQL string escaping and made character offsets consistent across Go, JavaScript, and Python implementations.

Full changelog

Version 1.0.1

Bug fixes

  • Consistent character offsets for non-ASCII input. The parser now scans input by Unicode code point in all three languages (Go scans as []rune, JavaScript as Array.from(text)), so Range offsets advance one step per character regardless of byte or UTF-16 width. Previously Cyrillic and other multi-byte/astral characters desynced offsets across the Go, JavaScript, and Python ports.

  • Code-point token offsets in tokenize(). tokenize() now reports start/end as Unicode code-point offsets in every language, identical across Python, Go, and JavaScript for all input. Previously Go emitted byte-width token spans and JavaScript emitted UTF-16-code-unit spans for non-ASCII (and astral) characters, breaking the gap-free offset invariant.

  • Valid PostgreSQL string escaping. The PostgreSQL generator now emits escape-string literals (E'...') for values that contain backslash escapes such as quotes or newlines. A plain '...' literal treats backslashes literally under standard_conforming_strings (the default), which could produce invalid SQL; values that need no escaping still render as plain '...'.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track FlyQL

Get notified when new releases ship.

Sign up free

About FlyQL

All releases →

Related context

Beta — feedback welcome: [email protected]