[Pdx-pm] (OT) SQL style question
david at kineticode.com
Thu Jan 13 15:27:38 PST 2005
On Jan 13, 2005, at 3:19 PM, Randall Lucas wrote:
> I recommend against this, even if all your target database platforms
> support escaped identifier names with periods in them. For one thing,
> Class::DBI (and/or at least some of its related modules) doesn't play
> nice with quoted names. I got a good ways into an implementation that
> worked with all of my own software, using odd but escaped names on
> Postgres, but found myself in a world of hurt when trying to use a
> number of automation tools for SQL.
Only an issue if you're using Class::DBI.
> If you have the luxury, ban leading, trailing, and double underscores
> in all db identifiers except for the prefixed names. That should
> preserve uniqueness of __ so that you can do a s/__/\./g to change
> names back.
Yes, that's where I'm leaning now. Then we just have to deal with the
overhead of that conversion for each column name.
> Having names that m/^\w+$/ will be a lot easier for you in the end, I
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 2369 bytes
Desc: not available
Url : http://mail.pm.org/pipermail/pdx-pm-list/attachments/20050113/bc0f8004/smime.bin
More information about the Pdx-pm-list