Re: [Sqlalchemy-tickets] [sqlalchemy] #2050: add explicit error when 'metadata' is used as a column name

[sqlalchemy <mi...@zz...>]

#2050: add explicit error when 'metadata' is used as a column name
---------------------------------+------------------------------------------
    Reporter:  guest             |       Owner:  chrisw                            
        Type:  enhancement       |      Status:  closed                            
    Priority:  medium            |   Milestone:  0.6.7                             
   Component:  declarative       |    Severity:  trivial - <10 minutes             
  Resolution:  fixed             |    Keywords:  PickleType declarative_base Column
Status_field:  completed/closed  |  
---------------------------------+------------------------------------------
Changes (by zzzeek):

  * status:  new => closed
  * resolution:  => fixed
  * status_field:  in progress => completed/closed


Comment:

 r11e40e2bb6fd
 r1fc57ead7b0c

 Yes I was going to mention, someday we might consider renaming this
 attribute to be `__metadata__` like the others, the rationale for
 `metadata` was that it would be more commonly accessed.   I didn't think
 that the other `__names__` names would be so widely used as accessors
 (i.e. people using `cls.__table__`, etc.) so if it were today, I'd have
 gone with `__metadata__`.   We already have a huge list of changes for 0.7
 (though mostly backwards compatible) but I don't know if I want to add
 another surprise on the heap just yet.

-- 
Ticket URL: <http://www.sqlalchemy.org/trac/ticket/2050#comment:3>
sqlalchemy <http://www.sqlalchemy.org/>
The Database Toolkit for Python