Hi Paul,
It seems for some strange reason the database world is stuck in the 70's
when it comes to naming conventions. I still see a lot of people designing
entire databases that are all caps and underscores, every column prefixed
with the first 3 chars of the table name, and the rest cryptic mashes of
letters to keep the name short. Drives me crazy and really irritates the OO
guys that think the database is screamming at them. LOL. Esspecially when
you gen OO models they need to go in and change all of the names. I have
found that using naming conventions from or similar to OO conventions makes
everything play nicer, and I can actually get an idea of what the column
means from its name.
"Paul Murray" <pemurray@staysystems.com> wrote in message
news:49ea29d7$1@forums-1-dub...
> Greetings all,
>
> I don't think I really want a case-sensitive database, but after reverse
> engineering, PD tells me that it is? What are the pros and cons, please?
>
> How would I prevent this? I don't see anything in the table referenced to
> suggest that it should be case sensitive.
>
> Thanks!!
>
> Paul
>
|