"Transactions involving multiple attached databases are atomic, assuming that the main database is not ":memory:" and the journal_mode is not WAL. If the main database is ":memory:" or if the journal_mode is WAL, then transactions continue to be atomic within each individual database file. But if the host computer crashes in the middle of a COMMIT where two or more database files are updated, some of those files might get the changes where others might not."
But also you can just install your own keyboard app. They will likely make a replacement version eventually, it's planned to replace the stock apps that are bad.
This reference from Germany indicates that self-defense is lawful even if it ends the attacker's life, as long as the violence is not excessive for the situation.
They'll always rule that the violence was excessive. They'll say you could've slapped him in the face or disarmed the attacker.
The only ones getting a free pass are criminals. When they shoot and kill each other judges usually rule that it was self-defense. Ordinary people...no such luck.
Besides in Europe you always have to use physical violence to kill someone because firearms are illegal.
They'd also have to update all their phone spec sheets -- not having the sandbox doubled graphene's battery life on my Pixel 6 Pro (in practice and vs. advertised specs).
I trust iOS with my banking and financial apps in a way that I would never trust Google, but I am under no illusion that any architecture can be completely secure.
On the Linux side, I have found SELinux maddening at times in forcing me to the syslog to enable and permit what I need the machine to do.
I have never seen anything this obstreperous in a BSD, but perhaps I have not looked with sufficient depth.
In any case, the Trust / SELinux / Enforcing status is a sizable advantage against iOS.
And null termination is guaranteed to work, because the only two characters forbidden in Unix filenames (for most varieties of Unix, I won't guarantee there aren't some weird variants out there) are / and null.
The only times I've needed something more than `find -print0 | xargs -0` has been when I need to apply logic to decide whether to process one of the files, in a way that's not easy to express in a `find` command. Then I write a small script with a for loop and if statements inside it.
But more people should know about `-print0`. It's the answer to 95% of the problems with `find | xargs`.
"Transactions involving multiple attached databases are atomic, assuming that the main database is not ":memory:" and the journal_mode is not WAL. If the main database is ":memory:" or if the journal_mode is WAL, then transactions continue to be atomic within each individual database file. But if the host computer crashes in the middle of a COMMIT where two or more database files are updated, some of those files might get the changes where others might not."
https://sqlite.org/lang_attach.html
reply