2 ms·
I believe record-oriented data sets only give you fixed but not arbitrarily/variably-sized extents. I.e., a given file (data set) is of one record type (sort of
by derefr 7y ago
I believe record-oriented data sets only give you fixed but not arbitrarily/variably-sized extents. I.e., a given file (data set) is of one record type (sort of like an RDBMS table is of one record type), and the record type then determines the extent size for the whole file.
Whereas, what I'm talking about, is more like what you get by having a sorted-set data structure in Redis, and putting arbitrary strings in it. Or storing data in LMDB with BASIC-like numeric labels as keys. Rather than a tabular representation, your data store is a heap, with a tabular index set aside to point into it.
(Of course, you can emulate arbitrary-length records over fixed-length records, as Postgres does with its TOAST tables, or—in the small—as UTF-8 does with runes. But in the record-orientation implementation, that’s something that would be exposed to the developer, requiring them to solve the problem themselves or through a library; rather than the file system just showing you arbitrary-length records from the start. And, if you can’t rely on other users doing that work, you can’t really use it as an interchange format.)