On 05/10/2010 18:03, Michael Bayer wrote:
Also, is there a 'trunk' or 'tip' anywhere now to put 0.7-targeted code?
there's not. You'd make a bitbucket repo and link to it on the trac ticket.
Done:
http://www.sqlalchemy.org/trac/changeset/6868:d8580d6765d4
Hi All,
Start off with a base.py module:
from sqlalchemy.ext.declarative import declarative_base
Base = declarative_base()
Now, say we have a module, a.py:
from sqlalchemy import *
from base import Base
class Something(Base):
__tablename__ = 'foo'
id = Column('id', Integer,
On Oct 5, 2010, at 11:04 AM, Chris Withers wrote:
Hi All,
Start off with a base.py module:
from sqlalchemy.ext.declarative import declarative_base
Base = declarative_base()
Now, say we have a module, a.py:
from sqlalchemy import *
from base import Base
class Something(Base):
On 05/10/2010 16:10, Michael Bayer wrote:
I think an exception should be raised if a class name already exists in
_decl_class_registry when the assignment is made in _as_declarative.
yeah definitely, though in 0.6 it needs to be a warning to start since some
folks might be doing this
On Oct 5, 2010, at 12:37 PM, Chris Withers wrote:
On 05/10/2010 16:10, Michael Bayer wrote:
I think an exception should be raised if a class name already exists in
_decl_class_registry when the assignment is made in _as_declarative.
yeah definitely, though in 0.6 it needs to be a warning
