Frectonz
sqlite doesn't use git, they use their own VCS called fossil 🤯
Not only do they have their own VCS but they also have their own parser generator.
Frectonz
Live stream finished (3 hours)
I learned a lot about SQLite even with just 3 hours of reading.
RTFM is not a meme people, do it.
RTFM is not a meme people, do it.
👍1
Jack's tweets seem to be some secret code, he's waiting for us to decipher.
X (formerly Twitter)
jack (@jack) on X
no state is the best state
Most of the stuff i send here is from twitter, yall should just create twitter accounts 😂
👍3
😐
> wakes up late
> needs to get to school by 2:30 for presentation
> takes a lada
> gets to the class
> no one is there
> checks telegram
> "class has been postponed to be at 7:00"
> wakes up late
> needs to get to school by 2:30 for presentation
> takes a lada
> gets to the class
> no one is there
> checks telegram
> "class has been postponed to be at 7:00"
The proper way to do IDs
1. Auto incrementing primary key
2. ULID visitor key
You shouldn't let anyone outside of the system know about the auto incrementing ID. This means you shouldn't use it in URLs, you shouldn't return it in your API responses. For all the above cases you should use a visitor key, which you store along wih the auto incrementing key. It's use is interfacing with the outside world, like in URLs and stuff. And finally you should only use the primary key for table relations.
1. Auto incrementing primary key
2. ULID visitor key
You shouldn't let anyone outside of the system know about the auto incrementing ID. This means you shouldn't use it in URLs, you shouldn't return it in your API responses. For all the above cases you should use a visitor key, which you store along wih the auto incrementing key. It's use is interfacing with the outside world, like in URLs and stuff. And finally you should only use the primary key for table relations.
👍4