Explore >> Select a destination
|
You are here 
|
serendipita.org | ||
| | | | |
www.ylva-publishing.com
|
|
| | | | | ||
| | | | |
www.iamnotauser.com
|
|
| | | | | It's important to avoid the word 'user' in our wardrobe as well! You can buy a Not a USER t-shirt directly from our on-line shop, choosing between | |
| | | | |
blog.sqlterritory.com
|
|
| | | | | [AI summary] This content appears to be a website's homepage with a menu, social media links, and cookie consent notice, likely related to SQL Server topics. | |
| | | | |
adriano.fyi
|
|
| | | Problem synopsis I'm a huge fan of sqlc's approach to code generation. I've seen sqlc called a reverse ORM, and I really like that moniker. However, as a sqlc newbie, I'm still discovering its edge cases. Today's edge case is using postgres UPSERT queries with sqlc. The crux is that when upserting, it's necessary for unique key conflicts to occur so that the UPDATE portion of the query executes. But non-null uuid Go types tend to have a zero-value of 00000000-0000-0000-0000-000000000000. This results in new records inserting with the uuid Go type's zero value, and every following new record upserts the existing zero ID record. | ||
