[sqlalchemy] documentation correction on declarative mixin

2010-07-09 Thread Randy Syring
http://www.sqlalchemy.org/docs/reference/ext/declarative.html#controlling-table-inheritance-with-mixins

In the second example, Engineer has __tablename__ = None
But, I think the point of that section, is that it wouldn't be
needed.  __tablename__ in Tablename should assign None anyway,
shouldn't it?

laggo on IRC confirmed and said I should post to the mailing list.

-- 
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to 
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.



Re: [sqlalchemy] documentation correction on declarative mixin

2010-07-09 Thread Michael Bayer

On Jul 9, 2010, at 4:32 PM, Randy Syring wrote:

 http://www.sqlalchemy.org/docs/reference/ext/declarative.html#controlling-table-inheritance-with-mixins
 
 In the second example, Engineer has __tablename__ = None
 But, I think the point of that section, is that it wouldn't be
 needed.  __tablename__ in Tablename should assign None anyway,
 shouldn't it?

sure the second two examples probably shouldn't have the __tablename__ on 
Engineer.

-- 
You received this message because you are subscribed to the Google Groups 
sqlalchemy group.
To post to this group, send email to sqlalch...@googlegroups.com.
To unsubscribe from this group, send email to 
sqlalchemy+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.