On Friday, December 20, 2024 at 5:49:04 PM UTC-6 Dan Kortschak wrote:
Almost certainly not. The point of module version specification is to
allow reproducible builds. Leaving this up to things outside the
build's dependencies makes this non-achievable.
Well, we agree then, but is this "tool
Hi Doug,
Consider this a drive by comment, but you might be able to create a version
of the nested module that does not have any code in it, and set up a
requirement cycle between the nested module and a new parent version.
I think there’s a general approach of creating a requirement cycle f
> I heard about SQLc a lot, but my question is how can I use it to manage
my database schemas with it, is it event possible?
sqlc works with a bunch of different migration tools:
https://docs.sqlc.dev/en/latest/howto/ddl.html#handling-sql-migrations
The one called "tern" is postgres-specific but
There are a couple of good options for schema management in Go.
Personally, I use goose with sqlc but you can use it with ORMs too.
On Sun, Dec 22, 2024, 08:46 Bhavesh Kothari wrote:
> Hello everyone,
> I'm new to go and have to work on a project from scratch.
> I looked into for various resour
Hello everyone,
I'm new to go and have to work on a project from scratch.
I looked into for various resources and learnt golang, also selected gin as
my project framework and pgx as my post-gres driver.
Now I'm looking out for guidance on how I can manage my database schemas
for this project.
I
> WHERE email = CASE WHEN sqlc.arg(email) = '' then NULL else
sqlc.arg(email) END
What database is that? If it's Postgres then I believe that expression
collapses to
WHERE email = NULLIF(sqlc.arg(email), '')
But wouldn't it be better to pass null explicitly, rather than assume
"empty stri
