Re: [Pytrainer-devel] Automated data migration

2011-08-02 Thread David García Granda
Hi Nathan, 2011/8/2 Nathan Jones : >>> For the second issue, I have added 'pytrainer.upgrade' to the list of >>> packages in setup.py. I am not sure if this is enough to entirely fix >>> this problem. >> >> It seems enough at least for installing sources and executing pytrainer ;) >> >>> Can you e

Re: [Pytrainer-devel] Automated data migration

2011-08-02 Thread Nathan Jones
>> For the second issue, I have added 'pytrainer.upgrade' to the list of >> packages in setup.py. I am not sure if this is enough to entirely fix >> this problem. > > It seems enough at least for installing sources and executing pytrainer ;) > >> Can you explain how you setup Pytrainer as a Python

Re: [Pytrainer-devel] Automated data migration

2011-07-29 Thread Nathan Jones
> BTW, Fedora has 2 packages: > > python-migrate > python-sqlalchemy These are the same as the package names in Ubuntu. It will be python-migrate that you need. > I need to have a look to documentation for dummies: > http://packages.python.org/sqlalchemy-migrate/versioning.html Reading through t

Re: [Pytrainer-devel] Automated data migration

2011-07-29 Thread David García Granda
Hi, > Good spotting. I have deleted the unused migrate directory. I don't > think this would have been causing any issues though because it did > not contain an __init__.py file. Definitely not, I just wondered if some files were missing there. > Did you install the > sqlalchemy-migrate dependen

Re: [Pytrainer-devel] Automated data migration

2011-07-29 Thread Nathan Jones
Good spotting. I have deleted the unused migrate directory. I don't think this would have been causing any issues though because it did not contain an __init__.py file. Did you install the sqlalchemy-migrate dependency? Hopefully this solves the first issue. For the second issue, I have added 'pyt

Re: [Pytrainer-devel] Automated data migration

2011-07-29 Thread David García Granda
Hi Nathan, > The new data upgrade functionality is available in revision 826. This > adds sqlalchemy-migrate as a dependency. > > Sqlalchemy-migrate uses a version table in the DB to keep track of the > schema version. Each time Pytrainer starts, the upgrade mechanism will > check this version num

Re: [Pytrainer-devel] Automated data migration

2011-07-29 Thread Nathan Jones
The new data upgrade functionality is available in revision 826. This adds sqlalchemy-migrate as a dependency. Sqlalchemy-migrate uses a version table in the DB to keep track of the schema version. Each time Pytrainer starts, the upgrade mechanism will check this version number, adding it if missi

Re: [Pytrainer-devel] Automated data migration

2011-07-15 Thread Nathan Jones
I've mostly done the work for splitting data migrations out into individual scripts for each schema version and automating this process using sqlalchemy-migrate. I hope to get this committed soon. Surprisingly, Pytrainer used to have a rudimentary version-by-version upgrade mechanism. In revision

Re: [Pytrainer-devel] Automated data migration

2011-06-01 Thread David Fraser
On Wednesday, June 1, 2011 at 10:41:29 PM, "Nathan Jones" wrote: > Thanks for the suggestion. I agree that it will be better to use an > existing library instead of crafting our own solution so I've had a > closer look at sqlalchemy-migrate. > > I was previously in favour of using the applicatio

Re: [Pytrainer-devel] Automated data migration

2011-06-01 Thread Nathan Jones
Thanks for the suggestion. I agree that it will be better to use an existing library instead of crafting our own solution so I've had a closer look at sqlalchemy-migrate. I was previously in favour of using the application version number as the DB schema number but, now that I think about how sqla

Re: [Pytrainer-devel] Automated data migration

2011-05-28 Thread David Fraser
Hi I think this is a great idea! I'm just wondering whether there aren't existing projects that could help us with this (something like sqlalchemy-migrate...) Cheers David - Original Message - From: "Nathan Jones" To: "pytrainer developers list" Sent: Friday, May 27, 2011 3:53:53 PM S