kphamilton wrote:
>
>I used the bin/export before I added the extend.py to any of the lists and it
>retrieved all of the necessary information.
OK. That makes sense.
BTW, just for curiousity, I actually tried a partial test on the
withlist suggestion I posted, and I found problems. In case anyo
I used the bin/export before I added the extend.py to any of the lists and it
retrieved all of the necessary information.
Mark Sapiro-3 wrote:
>
> kphamilton wrote:
>>
>>I have actually accomplished this! Woohoo! I did upgrade as you said to
>>MysqlMemberships.py.
>>
>>I accomplished the rest
kphamilton wrote:
>
>I have actually accomplished this! Woohoo! I did upgrade as you said to
>MysqlMemberships.py.
>
>I accomplished the rest in a different manner than you suggested, so I will
>share if others attempt this.
>
>I used export in the /bin folder to export all list data in xml format
I have actually accomplished this! Woohoo! I did upgrade as you said to
MysqlMemberships.py.
I accomplished the rest in a different manner than you suggested, so I will
share if others attempt this.
I used export in the /bin folder to export all list data in xml format.
I then wrote a python
Mark Sapiro wrote:
>
>
>from Mailman import mm_cfg
>from Mailman import OldStyleMemberships as OSM
>
>def move_members(mlist):
>if not mlist.Locked():
>mlist.Lock()
>for member in OSM.getMembers(mlist):
>if mlist.is
kphamilton wrote:
>
>I am attempting to migrate from using Mailman's flat file to store
>information about members towards a MySQL database backend instead. I have
>successfully configured it so that when I add a new member or change a
>member, it changes appropriately with the database table. The
Hello,
I am attempting to migrate from using Mailman's flat file to store
information about members towards a MySQL database backend instead. I have
successfully configured it so that when I add a new member or change a
member, it changes appropriately with the database table. The problem is
that
