Hi,
I have a database with a lot of schemas; now one schema has been added,
re-integrating a former separate database (of course, there are good reasons to
do so). This "new" schema contains very much data which is rarely changed;
thus, it would be sufficient to save it much less often than the
Hi,
I need to encrypt some fields in my database. The solution I came up with
is:
- create an additional field w/suffix "_encr" for every field which must be
encrypted;
- create update triggers which write the encrypted value into the new field
and null into the original field (not null constrain
Hi,
I have the need to encrypt some columns in some tables. With Postgres 7.4,
using a tablespace on an encrypted partition is not an option, right? Thus,
my idea is:
- put the encryption/decryption key in a temporary table
- create types for each type of data which must be encrypted (enc_numeri
Hi,
I have the need to encrypt some columns in some tables. With Postgres 7.4,
using a tablespace on an encrypted partition is not an option, right?
Furthermore, the content would be contained unencrypted in any database
dump.
Thus, my idea is:
- put the encryption/decryption key in a temporary
