winter.bsky.social
targeting
master
from
winter.bsky.social/core:
push-zrzuvtwqqook
sql.DB pools connections, which means that there's a good chance that
our foreign keys aren't actually being enforced, unless a goroutine
happens to be using the connection that was made when we set pragma foreign_keys = 1.
Signed-off-by: Winter winter@winter.cafe
`sql.DB` pools connections, which means that there's a good chance that
our foreign keys aren't actually being enforced, unless a goroutine
happens to be using the connection that was made when we set `pragma
foreign_keys = 1`.
Signed-off-by: Winter <winter@winter.cafe>
`sql.DB` pools connections, which means that there's a good chance that
our foreign keys aren't actually being enforced, unless a goroutine
happens to be using the connection that was made when we set `pragma
foreign_keys = 1`.
Signed-off-by: Winter <winter@winter.cafe>
`sql.DB` pools connections, which means that there's a good chance that
our foreign keys aren't actually being enforced, unless a goroutine
happens to be using the connection that was made when we set `pragma
foreign_keys = 1`.
Signed-off-by: Winter <winter@winter.cafe>
This does result in the removal of some options that aren't supported by
the SQLite driver [0], but IMO we can stick with the defaults for these.
[0]: https://github.com/mattn/go-sqlite3#connection-string
Signed-off-by: Winter <winter@winter.cafe>
yep, looks good!
tangled.org
anirudh.fi
Poke me when this is merged, I have another fix in this vein that I wish I could submit stacked but I can't because I made it as unstacked.