irelephant [he/him]
Hadriscus
MultipleAnimalsstrings “true” and “false” ofc like any sane developer
ValmondUse a CHAR(1) you can then use it as an enumeration.
Don’t use T/F for true/false use it for the actual sematic meaning for the thing that the Boolean is toggling. E g. S for subscribed, U for unsubscribed, or whatever.
It also means when you inevitably grow to needing a tri-state it makes sense.
I think you could use a CHECK constraint to effectively create en enum
Sometimes it’s 0 and 1
The Ramen DutchmanSmallest INT it can support and only ever use 0 and 1.
RustyNovaI 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
qevlarr
danWAL mode makes writes a lot faster, which is sufficient for a bunch of use cases. Writers do still need to wait, but they have to wait for a shorter duration. It’s still not the right choice for write-heavy use cases, of course.
create table boolean (
id integer primary key,
name text not null unique
)
insert into boolean (name) values ('true');
insert into boolean (name) values ('false');
create table document (
id integer primary key,
name text not null unique,
body text not null,
is_archived not null integer,
foreign key (is_archived) references boolean (id)
on delete cascade
on update no action
);
Solved.
Bonus: DBAs hate this one weird trick that can free up incredible amounts of disk space by deleting just two rows.