On Jan 11, 2009, at 6:13 AM, Cito wrote:
> > I wonder why declarative_base() doesn't simply set __tablename__ to > the name of the class by default (maybe translating camelcase to > lowercase with underscores), similar to how it is done in SQLObject > and Elixir. Also, the error message if you forget to set __tablename__ > is misleading, it should mention __tablename__ in declarative usage. __tablename__ is optional in the sense that you could alternatively specify __table__, or if you inherit then the table is optional entirely since you're using single table inheritance. I have heard the error message is misleading so we should fix that. As far as implicit tablename, it breaks the single inheritance scenario. but also besides that I made a comment on that here: http://www.sqlalchemy.org/trac/ticket/1270#comment:2 > Another idea (not sure if it really makes sense): In the order_by > clause, negative integers could be used for descending order, i.e. -2 > would work like desc(2). im not actually familiar with that technique ? does that mean ORDER BY 2 DESC or ORDER BY somecolumn DESC(2) ? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@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 -~----------~----~----~----~------~----~------~--~---
