Re: Perl to protect database field name info

No association tables to maintain - and my field name info is secure.

Betraying false sense of security. Your database is never being at risk because you reveal that your columns are named "Mom" and "Dad", but because it's environment isn't secure. While your technique is a nice idea, I'd label it "security by obscurity."

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re: Perl to protect database field name info

Replies are listed 'Best First'.
Re^2: Perl to protect database field name info by Joost (Canon) on Feb 12, 2007 at 23:43 UTC
agreed. using the correct DBI constructs and SQL (or better yet, use a wrapper like Class::DBI) you should never have any problem with this. and if you do have sql problems the OP's solution isn't really going to help. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^3: Perl to protect database field name info by Mutant (Priest) on Feb 13, 2007 at 10:01 UTC
or better yet, use a wrapper like Class::DBI Don't forget DBIx::Class, which IMHO surpassed Class::DBI in just about every way about a year ago. In response to the OP, you may also want to look at Catalyst. From your posts so far, it appears as if you're building web applications. Using a framework like Catalyst (along with Template Toolkit and DBIx::Class) will encourage you to keep your application, database and presentation logic separate (which will save you a lot of pain in the long run).	[reply]