Re: The wisdom of the object mentors (Was: Searching OO Associations with RDBMS Persistence Models)

From: x <x_at_not-exists.org>
Date: Wed, 14 Jun 2006 11:24:37 +0300
Message-ID: <e6ogt6$ruc$1_at_nntp.aioe.org>


<frebe73_at_gmail.com> wrote in message
news:1150221710.118378.182120_at_f6g2000cwb.googlegroups.com...
> > >> No knowledge of the *physical* schema. E.g. the table names, column
> > >> names, relationship tables, data forms, etc, etc.
> > > What is physical about names ?
> > You never change a column name?

> You don't change the name of a column by the same reason why you don't
> change a method name in an interface. What is the benefits with
> changing a column name?

>If you really need to change column (or table)
> names, I suggest the use of constants while building your SQL
> statements, or a framework (such as butler.sourceforge.net) that allows
> you to change names at any time.

Or better - variables.

> Or just go to the Edit menu and choose
> Search/Replace.

That would not be a good thing 'cause of name clashes. Received on Wed Jun 14 2006 - 10:24:37 CEST

Original text of this message