And that would be relevant if someone use sqlite as the default database backend for multiuser applications with stored procedures.
That's the problem here: Systems built on sharing the database over a networked filesystem, where one user can not just modify all the data, but can also execute code on all users machines.
SUSE takes snapshots before packages are installed. The package manager cannot tell if the disk will fill up as a result because on Btrfs the `df` command lies.
If its Btrfs root fills up and the OS writes to it, it 100% will self-destruct, and the `btrfs-repair` tool (`fsck` replacement) cannot fix drives and usually makes the corruption worse and renders the drive unreadable.
This is why in the earlier thread about swapfiles...
... I advised 2 commenters not to recommend keeping the OS and data in a single big volume. I got downvoted for it. I was rude. Well, I was, but I stand by my comments even though I'm sorry for my tone when I made them.
Though you don’t directly say it, your comment strongly implies that you can’t buy fractional shares of $VFIAX. (You can, same as $FXAIX, $VTSAX, etc.)
I understand that, for a stationary black hole without spin (which does not exist), an object that falls into it will freeze, then the image will redshift until it disappears.
I also understand that there is a cosmological (event) horizon, where galaxies freeze, then rapidly redshift in the same way. This happens because these distant objects are accelerated away from us faster than light.
It appears to me that we are seeing black hole event horizons from the outside, and the cosmological event horizon is seen from the inside.
The similarities do give one pause.
The mechanisms are different; one is gravity, and the other is dark energy.
A black hole stands still? Would that not defy gravity? I mean a black hole also loses energy, right? So I would not expect it to be completely still. After all if you lose energy, you may also lose mass and shape and size - E = mc².
Still from a far away observer. As matter gets close to the event horizon, its local clock as viewed from far away slows down to the point of freezing completely when it reaches the horizon (this you won't see from outside).
As this happens, what you see is a very hard dimming of the emited light and a very hard redshift because everything takes so long now (from the perspective of a far away observer) that the frequency of the light emitted and the luminous power emited basically go to zero (along with everything that has time in the denominator).
Not OP, but it’s not incompatible that dark-energy expansion (and ultimate big rip event) in a child universe correlates to the same process as black hole evaporation (and final event) for the originating black hole, if the “black hole universe” theory holds and they remain geometrically connected.
For my Oracle Linux systems, I rely on the vendor ReaR RPM package for the baseline backup. This is similar to the "Ignite" utility that I used in my HP-UX days.
This is two-fold useful, first as it enables boot from backup media for total recovery, second in that it creates a backup.tar.gz that holds everything that was not explitictly ignored in the /etc/rear/local.conf file.
I'm running Oracle databases on these systems (and the local.conf is configured to ignore the datafile directories). I have standby databases (not Dataguard in that I don't have online redolog replication) that allow me to recover them to the primary in a disaster, with some loss of committed transactions.
I finally have rsync configured for some scratch temporary files.
I have dallied with btrfs snapshot replication for home directories (in a loopback mount). My vendor support (via a CSI number) has been on and off, so I don't use btrfs in areas that we need it most.
My replacements do not like the complexity (and I am retiring).
While my karma might get incinerated with this quote, it is incisive on traditional architecture. The author is reviled by many.
“Yes, God damn it, the Parthenon!”
The ruler struck the glass over the picture.
“Look,” said Roark. “The famous flutings on the famous columns—what are they there for? To hide the joints in wood—when columns were made of wood, only these aren’t, they’re marble. The triglyphs, what are they? Wood. Wooden beams, the way they had to be laid when people began to build wooden shacks. Your Greeks took marble and they made copies of their wooden structures out of it, because others had done it that way. Then your masters of the Renaissance came along and made copies in plaster of copies in marble of copies in wood. Now here we are, making copies in steel and concrete of copies in plaster of copies in marble of copies in wood. Why?”
It's amusing to watch the movie version of The Fountainhead and see what are supposed to be Roarke's buildings. He likes the pedestal style, where the first floor is mostly open-work columns around a small lobby. Turns out this is terrible in cold or windy areas. Wind hits the side of the building and is forced down into the area around the lobby. Doors are forced shut by wind pressure. People are knocked off their feet. A strong wind in snow produces a horizontal blizzard.
The Meteorology Building (bldg 54) at MIT was built that way, with all of the above problems. Much embarrassment. Later, much computational fluid dynamics and, in 2019, a rebuild of the plaza level with more walls.
I don't know if dBASE variants support bind variables. That isolation is really required to avoid the "Bobby Tables" effect.
https://bobby-tables.com/
I'd prefer to see the dBASE language adapted to run on SQLite files, as they are a far more profound standard.
reply