Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-28 Thread Fil
We are currently two on irc on the #mailman channel trying to install this patch on our respective systems. Could anyone drop by and/or tell us where to find the latest series of updated files? thanks in advance -- Fil ___ Mailman-Developers mailing

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-28 Thread Fil
There is an issue with the flat mode, when you create the db according to the README file and choose PRIMARY KEY (listname, address) MySQL brings up the following error : ERROR 1071: Specified key was too long. Max key length is 500 So in fact the initial definitions of

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-28 Thread Fil
Okay I found out how to install this stuff for just one list (test list): use extend.py mechanism with: lists/test/extend.py containing the following lines: # import the MySQL stuff from Mailman.MysqlMemberships import MysqlMemberships # override the default for this list def extend(mlist):

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-27 Thread Adrian Wells
John W. Baxter [EMAIL PROTECTED] on Thursday, October 27, 2005 at 1:22 AM + wrote: On 10/26/05 6:06 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Actually, it is not really doing the right thing because it is not supposed to be aware of what's in the _BounceInfo class. The info that is passed

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-27 Thread Adrian Wells
Mark Sapiro [EMAIL PROTECTED] on Wednesday, October 26, 2005 at 9:06 PM + wrote: Adrian Wells wrote: OK. I imagine that not much can easily done to change this. I think that's right. The MemberAdaptor is not supposed to be in the business of determining when a _BounceInfo instance has

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-27 Thread Mark Sapiro
Adrian Wells wrote: It appears as though the MySQL VARCHAR type can preserve newlines http://dev.mysql.com/doc/refman/4.1/en/char.html. However trailing space is removed in this data type. If trailing space must be preserved, one could use the MySQL TEXT type

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-27 Thread Fil
A lot of good work on this MySQLMemberAdaptor! If you think it can make things easier and faster I'm willing to open a subversion repository to develop Mailman patches and plugins. Please tell. (I already have one running multiple projects on my server, so one more cannot hurt. It uses trac as a

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-27 Thread John Dennis
On Thu, 2005-10-27 at 09:25 -0700, Mark Sapiro wrote: There is an issue however in that the representation can exceed 255 characters if there is a cookie and/or a longish member address. The first reference above seems unclear on this. It says Values in VARCHAR columns are variable-length

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-27 Thread Mark Sapiro
Adrian Wells wrote: Mark Sapiro [EMAIL PROTECTED] on Wednesday, October 26, 2005 at 9:06 PM + wrote: Actually, it is not really doing the right thing because it is not supposed to be aware of what's in the _BounceInfo class. The info that is passed to it is a string representation of the

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-26 Thread Mark Sapiro
Adrian Wells wrote: Adrian Wells [EMAIL PROTECTED] on Monday, October 24, 2005 at 1:56 PM + wrote: I am not proficient in Python and don't completely understand how Mailman operates so I'm interested in finding some help to understand how information generated by registerBounce in Bouncer.py

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-26 Thread Fil
As an aside question I would ask: do you notice speed improvement by switching to MySQL-based membership? I have a big list of ~180k subscribers and unfortunately it is now *very* difficult to use the web interface to unsubscribe people. Right now I have to resort to command-line instructions

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-26 Thread Adrian Wells
Mark Sapiro [EMAIL PROTECTED] on Wednesday, October 26, 2005 at 3:45 PM + wrote: Adrian Wells wrote: Adrian Wells [EMAIL PROTECTED] on Monday, October 24, 2005 at 1:56 PM + wrote: I am not proficient in Python and don't completely understand how Mailman operates so I'm interested in

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-26 Thread Mark Sapiro
Adrian Wells wrote: Mark Sapiro [EMAIL PROTECTED] on Wednesday, October 26, 2005 at 3:45 PM + wrote: Now, MysqlMemberships.py doesn't work in the same way. its setBounceInfo and getBounceInfo methods take the attributes out of the _BounceInfo instance and store them separately in the

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-26 Thread John W. Baxter
On 10/26/05 6:06 PM, Mark Sapiro [EMAIL PROTECTED] wrote: Actually, it is not really doing the right thing because it is not supposed to be aware of what's in the _BounceInfo class. The info that is passed to it is a string representation of the _BounceInfo instance, and it should really just

Re: [Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-25 Thread Adrian Wells
Adrian Wells [EMAIL PROTECTED] on Monday, October 24, 2005 at 1:56 PM + wrote: I am not proficient in Python and don't completely understand how Mailman operates so I'm interested in finding some help to understand how information generated by registerBounce in Bouncer.py is supposed to reach

[Mailman-Developers] Mysql MemberAdaptor 1.61 and Mailman 2.1.6

2005-10-24 Thread Adrian Wells
Hello all. I have been working with Kev Green's MysqlMemberships.py Adaptor version 1.61 (SourceForge.net Mailman patch ID 839386) and Mailman 2.1.6 with Python 2.3.4. So far the adaptor has worked fairly well (with a minor patch to deal with one of the change made in Mailman 2.1.4, I believe,