Dmitry,

> > This may mean that without the ability to encrypt the database (or
> > fields in the tables) we could find that Firebird is no longer a
> > viable option. Sigh. The encryption facilities doesn't have to be
> > provided by the Fb project - a third party solution would be
> > acceptable (if it were at all possible). Encrypted backups will
> > probably be a must. Encrypted communication as well (ZeBeDee might
> > solve this). Disc encryption will not do (as far as I have
> > heard). I haven't seen the actual requirements yet so the above may
> > be a little fuzzy.
> >
> > Any thoughts/consolation/comments welcome.
>
> What's the problem? Encrypt any data before you put it into

database

> and relax.

Relax!?!!???

Not if you want to execute any SELECT SQL statements against the data,
which involve context evaluation.

Since the data will be encrypted outside the database, the engine will
not be able to decrypt the data in order to perform SQL statements.

By encrypting the data outside of the engine, you are really only using
the database engine as a data store, without any possibility of real
intelligence.


Sean