|
|
Posted by farrishj@gmail.com on 05/28/07 01:32
On May 27, 3:33 pm, e_matt...@hotmail.com wrote:
> I really like using the lowerUpper format because I find it annoying
> to type underscores all the time, and lowerlower becomes hard to
> read. However, it is more important to me that my live and local
> scripts are identical.
You have a powerful ally in Terry Halpin, the information modeling
guru. I think it's good practice; I happen to think it's easy to read
and see in a group of characters, which is important when authoring
and maintaining code.
> Does anyone else use the lowerUpper format successfully for things
> like mySql table names, when developing on windows and hosting on
> linux? Any suggestions? Thank you.
I use it. This is one of those areas where, if you have you SQL
interface properly configured as a singleton, you can parse and
transform (strtolower,strtoupper) on __call, instead of here and there
and everywhere. Using a library and filter contract pattern may be
useful, so that all table names are auto-transformed to lower or
upper. Unless you had a parsibly-transformative pattern (such as
String_To_Upper), I couldn't imagine how you'd accomplish what you're
describing using camel-case (bumpy-case, staggered-caps, lumpy-text,
whatever).
Navigation:
[Reply to this message]
|