| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2009-07-16 | Non-trivial changes to the event handling code: | Bharat Mediratta | |
| 1) The item_updated event no longer takes the old and new items. Instead we overload ORM to track the original data and make that available via the item. This will allow us to move event publishing down into the API methods which in turn will give us more stability since we won't require each controller to remember to do it. 2) ORM class now tracks the original values. It doesn't track the original relationships (no need for that, yet) 3) Added new events: item_deleted group_deleted user_deleted | |||
| 2009-05-13 | Gee it's May already. Update copyright to 2009. | Bharat Mediratta | |
| 2008-12-09 | Move code to delete users and add/remove users from groups into the | Bharat Mediratta | |
| model. | |||
| 2008-11-18 | Synchronize the model rules with the database definitions and vice-versa. | Tim Almdal | |
| 2008-11-14 | Change quotes style | Bharat Mediratta | |
| 2008-11-05 | The start of the user module. At this point, it shows up on the scaffolding ↵ | Tim Almdal | |
| screen and you can install and uninstall it. Which creates the tables, defines 2 groups (adminstrator, registered) and one user (admin). | |||
