From: Johan De Meersman
Date: June 17 2011 6:20am
Subject: Re: Encoding "Table Name" and "Filed Name"
List-Archive: http://lists.mysql.com/mysql/225279
Message-Id: <790cffdd-3402-4cc8-986c-fca5e7b9057d@zimbra>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


----- Original Message -----
> From: "Vikram A" <vikkiatbipl@stripped>
> 
> My question is, DO i face any negative project=C2=A0management problems b=
y
> doing this? Pleas share your=C2=A0experience=C2=A0on this aspect and comm=
end
> our idea.

Seems... a bit pointless, no? If someone has access to the database, they c=
an still see the data. If someone has access to the code, they can still fi=
gure out the naming scheme. If, for some reason, you have to do manual look=
ups (think debugging, custom reporting, ...) you're making your own life ha=
rd.

If you don't want people to see your data, manage your accounts. If people =
leave, delete their accounts. Make sure your code prevents SQL injections (=
use bind variables and so on). Firewall off your server from everything but=
 the application server. Et cetera ad nauseam.

There's plenty of security recommendations, but I've never heard of anyone =
encrypting their table and field names. It sounds like something upper mana=
gement would come up with :-)


-- 
Bier met grenadyn
Is als mosterd by den wyn
Sy die't drinkt, is eene kwezel
Hy die't drinkt, is ras een ezel