[sqlalchemy] Re: Seperate History Tables

2009-03-30 Thread Suha Onay
It is done now. Thank you for all your help. Suha On Mon, Mar 30, 2009 at 17:06, Michael Bayer wrote: > > > On Mar 30, 2009, at 5:10 AM, Suha Onay wrote: > > > The problem is i defined the history class with the following way > > (examining the test_versioning file): > >

[sqlalchemy] Re: Seperate History Tables

2009-03-30 Thread Michael Bayer
On Mar 30, 2009, at 5:10 AM, Suha Onay wrote: > The problem is i defined the history class with the following way > (examining the test_versioning file): > -- > Base = declarative_base(metaclass=VersionedMeta) > > class User(Base): > __tablename_

[sqlalchemy] Re: Seperate History Tables

2009-03-30 Thread Michael Bayer
On Mar 30, 2009, at 4:32 AM, Suha Onay wrote: > İnstalled nose and tested: no error > It is OK now. > > To make it easy for the developers not to care about the history > tables and versioning, is it possible not to define _history models > manually and make history_meta to generate them aut

[sqlalchemy] Re: Seperate History Tables

2009-03-30 Thread Suha Onay
The problem is i defined the history class with the following way (examining the test_versioning file): -- Base = declarative_base(metaclass=VersionedMeta) class User(Base): __tablename__ = 'users' id = sa.Column(sa.Integer, primary_key=True)

[sqlalchemy] Re: Seperate History Tables

2009-03-30 Thread Suha Onay
İnstalled nose and tested: no error It is OK now. To make it easy for the developers not to care about the history tables and versioning, is it possible not to define _history models manually and make history_meta to generate them automatically? Suha On Fri, Mar 27, 2009 at 20:09, Michael Bayer

[sqlalchemy] Re: Seperate History Tables

2009-03-27 Thread Michael Bayer
install nose and type "nosetests". Suha Onay wrote: > > The version is ok: 0.5.3 > The problem is I don't know how to do the unit tests: no tests package. > from tests import eq_, Comparable > > How can i do the unit tests? > > Suha > > > > > On Thu, Mar 26, 2009 at 19:04, Michael Bayer > wrot

[sqlalchemy] Re: Seperate History Tables

2009-03-27 Thread Suha Onay
The version is ok: 0.5.3 The problem is I don't know how to do the unit tests: no tests package. from tests import eq_, Comparable How can i do the unit tests? Suha On Thu, Mar 26, 2009 at 19:04, Michael Bayer wrote: > > not sure.  make sure you're on 0.5.3.   do the unit tests included wit

[sqlalchemy] Re: Seperate History Tables

2009-03-26 Thread Michael Bayer
not sure. make sure you're on 0.5.3. do the unit tests included with the recipe pass ? Suha Onay wrote: > Thanks for the recipe.I faced with an error. > > The model is now: > -- > from history_meta import VersionedMet

[sqlalchemy] Re: Seperate History Tables

2009-03-26 Thread Suha Onay
Thanks for the recipe.I faced with an error. The model is now: -- from history_meta import VersionedMeta Base = declarative_base(metaclass=VersionedMeta) class User(Base): __tablename__ = 'users' id = sa.Column(

[sqlalchemy] Re: Seperate History Tables

2009-03-25 Thread Michael Bayer
I've placed a recipe for this on the wiki at http://www.sqlalchemy.org/trac/wiki/UsageRecipes/LogVersions . On Mar 25, 2009, at 10:12 AM, Suha Onay wrote: > > Hi, > > I am using sqlalchemy for a while in a project. > The project has lots of models like User: > --