Explore >> Select a destination
|
You are here 
|
daudix.one | ||
| | | | |
carlschwan.eu
|
|
| | | | | A month ago, I started working on a new application to manage your passwords in Plasma. And while still at a PoC status, this weekend, it finally started to look like something almost usable, so it sounded like a good occassion to write a small blog post about it. The current name is "Keychain" or "Plasma Keychain" but this is subject to change and suggestions are more than welcome. My end goal is to provide a more future proof replacement to the ageing KWallet application. From a technical point of view, this is a fork of the internal of KeepassXC with a Kirigami GUI completely written from scratch. This means it uses the standardized Keepass format to store the passwords in the database which is implemented by many applications including on other platforms... | |
| | | | |
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. | |
| | | | |
rolle.design
|
|
| | | | | It's time to revive my international WordPress blog. This blog post exists only for testing purposes. I want to see those webmentions below. A side note, I also changed "Comment on Twitter" to "Comment on Mastodon" link, as I ditched the hell site. Stay tuned. | |
| | | | |
adriano.fyi
|
|
| | | Fly.io Postgres failover fix (flyctl pg failover) This is a note to myself, meant to be succinct and helpful. I'm sharing it publicly to save others time. Most of the time Fly.io works as I expect it to, but occasionally there are edge cases that lack documentation, public announcements, or both. It's possible that at some point Fly.io announced a breaking change and I missed it, but the behavior I observed deserves more than an announcement or silently released documentation. | ||
