On Wednesday 04 February 2015 01:23 PM, Andrew Stuart wrote:
Anyone got quick tips for dropping the entiure database and recreating it
with alembic?
Just delete the database - `var/data/mailman.db`. It would automatically
be (re)created the next time you start mailman. No need to alembic for
Hi Andrew,
Thanks for the detailed response. I'll try to find some time tonight to go
through your recipe step-by-step. Some questions in the meantime:
On Feb 04, 2015, at 09:26 PM, Andrew Stuart wrote:
For a clean start I deleted my Mailman 3 installation. I downloaded the
latest version
I notice that when a user is deleted, the uid record remains.
Is this because there is a bug in which the uid should be deleted but is not?
or is this intentional behaviour to prevent the uid from being recreated as a
duplicate?
My testing code does large numbers of creations and deletions of
After unlinking an address from a user, there is an address in the addresses
table that is orphaned - i.e. it does not have a linked user. This is the
expected behaviour (I think) - that’s fine, no problems at this point.
However, I can’t see a way to delete these addresses via the REST API.
After executing the curl command:
curl -X POST --data email=mailmanad...@example.org --header authorization:
Basic cmVzdGFkbWluOnJlc3RwYXNz http://localhost:8001/3.0/users
The log file adds the following:
Feb 04 11:30:05 2015 (17776) BEGIN (implicit)
Feb 04 11:30:05 2015 (17776) SELECT
It’s reproducible for me, I’m not sure what might be different in our
configurations.
For a clean start I deleted my Mailman 3 installation. I downloaded the latest
version and installed it. I deleted and recreated my databases after first
making sure they were empty.
To see the problem I
After a bit of deep cave diving into the code I suspect it’s this in
model/usermanager.py
This function appears to create a user before it checks to see if the address
exists, with the result that multiple users are created when the address
already exists.
@implementer(IUserManager)
class
