I think you got the wrong caption. It's the world if SQLite supported multiple concurent writes.
Stupid transaction deadlocks...
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
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.
This is sqlite's intended use case. To replace configure files and local data
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.
Would this make 0 = true and 1 = false?
You're right, that's way too simple. Definitely need to rotate the booleans daily. For... security. Yeah, security.
That on delete cascade is evil. I love it.
What do you use instead of booleans ? floats ?
strings "true" and "false" ofc like any sane developer
good fucking god
it allows for mood changes, some parts of the code can check charAt(0) == 't'others can do val != 'false' just let it flow.
lord mary joseph make it stop
And for double fun if the output doesn’t matter you can make if endsWith(“e”).
I got a better one: O for true and N for false.
Seen in production for quite important stuff (payment requests).
O is from Oui, N from Non, of course!
😐🫤
The system I work on uses "Y" and "N".
This is awful and aweful at the same time.
Non affective, non effective.