[sqlalchemy] Re: whats going to break in 0.4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 5, 2007, at 6:00 PM, Michael Bayer wrote: On Jul 5, 5:46 pm, Barry Warsaw [EMAIL PROTECTED] wrote: What I mean by that is that Mailman has at least three separate related collections of data: mailing lists, users, and messages. It should

[sqlalchemy] Re: whats going to break in 0.4

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jul 3, 2007, at 8:14 PM, jason kirtland wrote: Barry wrote: I have exactly the same architecture and exactly the same question. In fact, my goal in Mailman 3 is to be able to let sites configure the system to use any supported database

[sqlalchemy] Re: Concurrency problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Apr 3, 2007, at 9:35 AM, Michael Bayer wrote: OK, yes, im sorry about the lack of docs for isnew...sometimes i subconsciously want to see how long it takes for someone to ask me about something (bad habit) although in this case that flag is

[sqlalchemy] Concurrency problem

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello SQLAlchemists, Over in the Mailman project, we've hit a concurrency problem that we don't know how to (properly) fix. Any suggestions you might have would be greatly appreciated. The full thread starts here:

[sqlalchemy] import logging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Does sqlalchemy intend to expose a logging module that isn't Python's standard logging module when one does from sqlalchemy import *? AFAICT, this isn't supposed to be part of the public interface of the top level sqlalchemy package so it

[sqlalchemy] Re: import logging

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 16, 2007, at 3:18 PM, Michael Bayer wrote: it does not intend to, nor does it intend to export types which may also be happening. im not exactly sure how logging is getting into the actual list of * exports. I haven't looked at the

[sqlalchemy] Mailman trunk now backed by SQLAlchemy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I thought I would let you know that I've committed a bunch of changes to the Mailman svn trunk that integrates a SQLAlchemy storage for all mailing list data. My goal was to be able to make this change without disrupting the basic

[sqlalchemy] Re: Mailman trunk now backed by SQLAlchemy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Jan 1, 2007, at 3:24 PM, Michael Bayer wrote: I may put a note on the SQLAlchemy site about this, its big news ! Please feel free Mike, and thanks! - -Barry -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin)