[Mailman-Developers] ORM layer transition

[Guillaume Libersat]

Hi,

First, thanks for this wonderful enhancement, it's gonna make a lot of
things much easier and reliable!
I've just tried the branch and wanted to point out that I had to add :

"from __future__ import print_function"

at the beginning of:
 - src/mailman/bin/checkdbs.py
 - src/mailman/bin/bumpdigests.py

otherwise it would complain about using "file=" in the print function
(using python2.x).

It looks to run smoothly in my test environment, how crazy is it to try
it on the production server? Any chance to corrupt the DB? :)

I'd like to explore the possibility to write a migration script from
sqlite to postgres with the new ORM (saw this:
https://zignar.net/2011/11/01/copy-data-from-mysql-to-postgres-using-sqlalchemy/
). If someone is already working on this, please tell me!

Cheers,

Guillaume




Le 01/11/2014 20:16, Stephen J. Turnbull a écrit :
> Barry Warsaw writes:
>
>  > I am happy to announce that the MM3 trunk has been ported to
>  > SQLAlchemy (SA).  The full test suite completes against both SQLite and
>  > PostgreSQL as back-ends, and I would expect that with a little bit of work
>  > (contributions welcome!) any other back-end supported by SA should work too.
>
> Huzzah!  Happy Mailman Day!  (Although it isn't here any more. :)
>
>  > Without the contributions of both Abhilash and Aurélien, this port would not
>  > have happened.  Kudos to them,
>
> +1 !!
>
> Steve
>
> _______________________________________________
> Mailman-Developers mailing list
> Mailman-Developers at python.org
> https://mail.python.org/mailman/listinfo/mailman-developers
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/glibersat%40sigill.org
>
> Security Policy: http://wiki.list.org/x/QIA9

-- 
http://sigill.org