[ckan-dev] sqlalchemy migrate, dependency issues.

[David Read]

David,

I see no problem with changing setup.py to specify the newer versions.
The question is whether we're happy to run the migrate tool in all our
CKAN databases, since some of them may be running old CKAN versions,
perhaps due to old-style plug-ins and customisations. I think it is
worth doing a backup of eu3 and the databases, followed by trying
migrating them all. (It would be useful if we had nagios monitoring of
all the supported CKAN instances so that we can check we don't leave
any with any problems, but for now we can refer to
http://wiki.okfn.org/ckan/instances )

David


On 25 January 2011 22:05, David Raznick <kindly at gmail.com> wrote:
> Hello
>
> I have been wasting a lot of time trying to get migrations to work.
>
> There are two major issues.
>
> * later versions of sqlalchemy 0.5+ are incompatible with the migrate
> version currently used.  The later versions of migrate are also incompatible
> with earlier sqlalchemy versions.   I do not think there is a way to specify
> such dependencies in setup.py.
>
> * If we want to use the new migrate that works on 0.5+ we need to run a
> conversion process on our repository.
> http://packages.python.org/sqlalchemy-migrate/tools.html.  The new
> repository is not backwards compatible.  For this there is the option of
> having 2 repositories and keeping them both updated (but I do not recommend
> it)
>
> The only sane option seems to be forcing a sqlalchemy upgrade to everyone at
> some time convert the repository.
>
> Shall we do this now?  Any advise welcome?
>
> Thanks
>
> David
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
>
>