Mark O'Donohue wrote:

>Specifying that certain fields are stored encrypted and/or compressed
>could be useful.
>
>

This is highly problematic. First, most symmetric cyphers including DES
and AES, are block cyphers that will wreak havoc with the ODS. Rounding
all fields to 8 bytes (DES) or 16 bytes (AES) is going to be a mess.
Second, encrypting a field will require that the index also be
encrypted. Third, how can triggers, validation expressions, and
constraints be evaluated without access to the field.

Table level encryption is a little more feasible since it is all or
nothing. But what is poor gbak to do?