On Wed, Sep 23, 2009 at 4:21 PM, D'Arcy J.M. Cain <da...@druid.net> wrote: > In any case, I have a strong philosophical objection to using the same > name to refer to two different things regardless of any operational > issues. The manager.firstname and employee.firstname are not the same > thing and should have different names to reflect that.
They are in separate tables, that should be enough to reflect the fact that they're not the same thing. > A similar issue comes up in the classic situation of the inventory table > price field and the sale item price field. They sound like the same > thing but they are not. One is the current price in the catalogue and > the other is the price it was sold for at a particular time. They need > different names for that reason. I am not sure if you're talking about two different tables (inventory and sale?). If you meant a single table; I would hope you don't have two columns, with the same name, in a single table. If you were talking about two different tables, see my above comment. -- http://mail.python.org/mailman/listinfo/python-list
