For a variety of reasons I've set a personal best for time in large hospitals in the last year. They can be very difficult to navigate in the best of times, much less in the less-than-ideal mental state that often accompanies time in a hospital.
I thought the same. Having said that, the parenthesis in the example are really wrong for what they were trying to convey. I suspect that they built this sql sample for the document and made some mistakes in its generation.
Perhaps I could say, it isn't just generated--it is also hallucinated!
I want one that is shaped like the USB-C port. Like it was extruded from the port. About as long as a key, maybe a shorter key, like a mailbox key. Has a rounded end with a hole to make a very sturdy keyring hole. Capacity is limited to what would be reliable and not overheat. <1g.
It sounds like you're describing the yubikey 5c form factor. Unfortunately I haven't been able to find a flash drive matching that form factor in my years of searching.
That is a very reductionist view and not particularly useful either. It shares elements with versioning and you could likely implement this using explicit versioning, but it is completely independent of it.
The main difference I see is that of focus here the focus is to migrate a database without downtime or excessive global locks, keeping multiple versions of the schema is a detail.
Versioning is a concept where each version lives in non-intersecting time intervals.
This concept is completely focusing on the fact that your structures lifetimes must absolutely have non-empty intersections. It's close to the opposite.
> "Versioning is a concept where each version lives in non-intersecting time intervals."
Is it? Node.js publishes "Current", "LTS" and "Maintenance" versions, and there's always a reasonable time interval during which consumers typically upgrade from eg Maintenance to newer LTS or even Current. From the publishing side, that's very similar to "expand and contract", in temporarily expanding what's supported to include Current, and dropping support for oldest versions leaving Maintenance. It's continuous instead of ad hoc, and there are more than 2 versions involved, but the principle is basically the same (at least if you squint).
Though I guess if you're talking strictly about schema management strategies, then yeah, "versioning" might be very different from "expand contract", as you noted.
I would change my name. Family tradition isn't worth the hassle. The older people in my family would eventually get over it. This harassment will not stop.
reply