Hi Jim,
I don't want to change ODS for saving one byte per page.
I want to change sources to be able implement different
encoder (put name that you want) - change ODS.
For some encoder is frangmentation lost 1-2 byte, for another
can be more.
For some encoder is easy to do reverse parsing, for
I regret both that I don't have a copy of Firebird source on the boat or
access to adequate bandwidth to get it, so I'm not in a position to comment
on tge existing code one way or another. But as I understand your
proposal, you are suggestion the the ODS be changed to save (at most) one
byte per
Index and blob garbage collection doesn't take into accout data in undo log
---
Key: CORE-4701
URL: http://tracker.firebirdsql.org/browse/CORE-4701
Project: Firebird Core
OK, I think I understand what you are trying to do -- and please correct me if
I'm wrong. You want to standardize an interface between an encoding and DPM,
separating the actual encoding/decoding from the fragmentation process. In
other words, you want to compress a record in toto then let
Sorry to continue to meddle, but once ideas start flowing, it's hard to stop
them.
If anyone wanted to implement user defined record encodings, here is one way to
do it:
1. Add a clause to create table to specify an encoding name
2. Add a parameter to the configuration files to map
