news — October 18, 2023
We’ve got a major release coming soon that we’re very excited about, because it will include a new query analysis engine that resolves a ton of outstanding issues. So stay tuned for that.
To go along with that release we’ve opened up our sqlc Cloud dashboard for early access, and you can sign up here: https://dashboard.sqlc.dev. It’s pretty barebones at the moment, but you can create an organization which will include a default project and within that project you can create auth tokens to add to your sqlc configuration as needed.
The features of sqlc which require an auth token today are managed ephemeral databases (for use with sqlc vet or your own testing purposes), project uploads, and remote codegen execution.
We know that adopting these new features can be confusing, so please post in the sqlc Discord server or send us an email at hello@sqlc.dev if you have any questions or issues getting started.
We’ve signed up as @sqlcdev on X/Twitter and @sqlc.dev on BlueSky. Go ahead and give us a follow for more frequent updates.
It was so nice to meet so many of you at GopherCon a few weeks ago, and to hear about how you’re using sqlc (or in one case how your corporate overlords won’t let you use sqlc). We especially appreciated Johan Brandhorst-Satzkorn’s presentation about WASM and WASI support in Go 1.21, which called out sqlc’s WASM-based plugin system as a leading use-case driving his work.
Speaking of plugins, we’ve been working a little bit on cleaning up the plugin interface in anticipation of expanding sqlc’s language support. And we’ve seen a few new plugins in the wild that you might find useful:
Before we go, we’d like to call out a few new proposals that could use some more community feedback. If you have a minute to read, consider and comment on whether these enhancements are useful (or not) to you and your team we’d appreciate it.
< All posts