Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Another .one -> .find_one | Elrond | 2012-03-13 | 1 | -2/+6 |
| | | | | | | | | | | | | | | | | | Same idea as in the previous commit. Joar caught this one. To reproduce 1. Create a user with an all-decimal ObjectId in mongo 2. Login using that user, while mongodb is enabled. 3. Switch instance to sql. 4. Restart. 5. Refresh any page. This will error, because no user with that object id exists any more. While around, improved logging. | ||||
* | It's 2012 all up in here | Christopher Allan Webber | 2012-02-02 | 1 | -1/+1 |
| | |||||
* | Drop sessions with invalid ObjectIds | Elrond | 2012-01-14 | 1 | -4/+8 |
| | | | | | | | | The session can contain invalid objectids when switching a more or less live instance (with logged in users) from mongo to sql or vice versa. So drop the complete session and force the user to login again. | ||||
* | Finished splitting util.py into separate files. | Aaron Williamson | 2011-10-01 | 1 | -0/+37 |