irelephant [he/him]@lemmy.dbzer0.com to Programmer Humor@programming.dev · 21 days ago: (lemmy.dbzer0.comimagemessage-square29linkfedilinkarrow-up1286arrow-down11
arrow-up1285arrow-down1image: (lemmy.dbzer0.comirelephant [he/him]@lemmy.dbzer0.com to Programmer Humor@programming.dev · 21 days agomessage-square29linkfedilink
minus-squareRustyNova@lemmy.worldlinkfedilinkarrow-up45·21 days agoI think you got the wrong caption. It’s the world if SQLite supported multiple concurent writes. Stupid transaction deadlocks…
minus-squareirelephant [he/him]@lemmy.dbzer0.comOPlinkfedilinkarrow-up10·21 days agoIn my case, I want to use sqlite locally, for development, but I don’t want to add a load of jank to handle booleans for sqlite.
minus-squareRustyNova@lemmy.worldlinkfedilinkarrow-up14·21 days agoI use rust’s SQLx which map bools to numbers so it must be a problem with your connector maybe
minus-squareirelephant [he/him]@lemmy.dbzer0.comOPlinkfedilinkarrow-up4·21 days agoYeah I should probably open an issue.
minus-squareWhyJiffie@sh.itjust.workslinkfedilinkEnglisharrow-up1arrow-down1·21 days agousername checks out so it must be a problem with your connector maybe or with their programming language
minus-squareRustyNova@lemmy.worldlinkfedilinkarrow-up2·21 days agoI actually started using rust well after picking this username :P
minus-squarenilloc@discuss.tchncs.delinkfedilinkEnglisharrow-up7·21 days agoThat’s what I like about Ruby ORMs. They did all the conversion for you, and you could have SQLite on your dev box, Postgres on the test server and MySQL on the annoying production host that wouldn’t run anything else. This was 18 years ago though.
minus-squareℍ𝕂-𝟞𝟝@sopuli.xyzlinkfedilinkEnglisharrow-up1·18 days agoAre not all ORMs like that? I only used ActiveRecord before fucking off from backend 10 years ago
minus-squareqevlarr@lemmy.worldlinkfedilinkarrow-up2·21 days agoThis is sqlite’s intended use case. To replace configure files and local data
I think you got the wrong caption. It’s the world if SQLite supported multiple concurent writes.
Stupid transaction deadlocks…
In my case, I want to use sqlite locally, for development, but I don’t want to add a load of jank to handle booleans for sqlite.
I use rust’s SQLx which map bools to numbers so it must be a problem with your connector maybe
Yeah I should probably open an issue.
username checks out
or with their programming language
I actually started using rust well after picking this username :P
That’s what I like about Ruby ORMs. They did all the conversion for you, and you could have SQLite on your dev box, Postgres on the test server and MySQL on the annoying production host that wouldn’t run anything else.
This was 18 years ago though.
Are not all ORMs like that? I only used ActiveRecord before fucking off from backend 10 years ago
This is sqlite’s intended use case. To replace configure files and local data