This was a follow up to a problem I raised to another proposal. I thought
the context was clear, bu apparently not... So here's the context.
Data compression has a huge effect on performance. Reducing the physical
size of the data reduces database size and the number of pages to be read
to fetc
What problem are you trying to solve?
What's the benefit? Are you trying to transfer inability of the product
designers to the user? How he wisely can chose that?
Can you start from the requirements instead of the design?
Adriano
On 28-02-2015 22:27, Jim Starkey wrote:
> Sorry to continue to
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 en
