Skip to content

v0.47.4
Compare
Choose a tag to compare
@neilotoole neilotoole released this 10 Feb 05:58
· 53 commits to master since this release
v0.47.4
9bb4185
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Learn about vigilant mode.

Patch release with changes to flags. See the earlier v0.47.0 release for recent headline features.

Added

  • By default, sq prints source locations with the password redacted. This is a sensible default, but there are legitimate reasons to access the unredacted connection string. Thus a new global flag --no-redact (and a corresponding redact config option).

    # Default behavior: password is redacted
$ sq src -v
@sakila/pg12  postgres  postgres://sakila:xxxxx@192.168.50.132/sakila

# Unredacted
$ sq src -v --no-redact
@sakila/pg12  postgres  postgres://sakila:p_ssW0rd@192.168.50.132/sakila

  • Previously, if an error occurred when verbose was true, and error.format was text, sq would print a stack trace to stderr. This was poor default behavior, flooding the user terminal, so the default is now no stack trace. To restore the previous behavior, use the new -E (--error.stack) flag, or set the error.stack config option.

Changed

  • The --src.schema flag (as used in sq inspect, sq sql, and the root sq cmd) now accepts --src.schema=CATALOG.. Note the . suffix on CATALOG.. This is in addition to the existing allowed forms SCHEMA and CATALOG.SCHEMA. This new CATALOG. form is effectively equivalent to CATALOG.CURRENT_SCHEMA.

    # Inspect using the default schema in the "sales" catalog
$ sq inspect --src.schema=sales.

  • The --src.schema flag is now validated. Previously, if you provided a non-existing catalog or schema value, sq would silently ignore it and use the defaults. This could mislead the user into thinking that they were getting valid results from the non-existent catalog or schema. Now an error is returned.

Assets 18
Loading