Re: Column naming convention good or bad?

>Yes, it's bad. Think about what happens when a column changes type
>from integer to long. If you prefixed it with "int", you have to
>change it to "lng".
>
>Now your views don't work, because they're looking for "int". Any
>client software that's based on those views breaks, too.

if you change a type from int to long (i.e. i32->i64) your clientsw will break anyway if you don't change it

>On top of all that, it reveals storage-level details--one of the
>things relational systems are supposed to hide from us.

huh. :-) ever seen users joining varchars with numbers?

types are not a storage detail but a domain classification.  

ciao, jan

http://www.rsp.de/

rs&p-Dossier: Geschäftsprozeßgesteuerte Schriftguterstellung. Received on Thu Nov 16 2000 - 21:34:39 CET