e. [...]
How about typing the "WHERE" part of the statement first, then
'left-arrowing' back to the start of the statement and do "DELETE FROM
..." *last*?
Dave.
--
Dave Ewart
[EMAIL PROTECTED]
Computing Manager, Epidemiology Unit, Oxford
Cance
tly
possible; you just need to decide what you're going to use to decrypt it
afterwards.
Dave.
- --
Dave Ewart
[EMAIL PROTECTED]
Computing Manager, Epidemiology Unit, Oxford
Cancer Research UK
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2CFD 694D E370
-BEGIN PGP SIGNATURE-
Version: G
milar legislation in Italy and elsewhere.
Suggestions:
1. You need to decide which fields in the database should be encrypted.
2. Perhaps keep all 'personal' data in a separate table and control
access to that table more closely with database permissions.
Optionally, encrypt the contents
llow this - there's no point AT ALL in using LoopAES if you
can mount the encrypted partitions without needing manual intervention
at boot time.
Dave.
--
Dave Ewart
[EMAIL PROTECTED]
Computing Manager, Epidemiology Unit, Oxford
Cancer Research UK
PGP: CC70 1883 BD92 E665 B840 118B 6E94 2
On Friday, 05.03.2004 at 12:51 +, Silvana Di Martino wrote:
> Alle 09:51, venerdì 5 marzo 2004, Dave Ewart ha scritto:
> > I guess there may similar legislation in Italy and elsewhere.
>
> Actually, the Italian law is an implementation of a EU directive
> strictly inspired
uestion.
But as you say, encrypting 'the whole database' in some way is probably
safest ...
If you find any 'automated' front-end to do this at the database-level,
rather than something like loopback at the filesystem level or at the
field level for specific fields, I think th
the server/disk.
If you're using LoopAES, it should *require* manual intervention, i.e.
passphrase to be entered. If you want the system to boot up
automatically, using LoopAES is redundant and so should not be used.
Dave.
- --
Dave Ewart
[EMAIL PROTECTED]
Computing Manager, Epidemiology
