- 16 Apr, 2015 1 commit
-
-
Aurel authored
-
- 15 Apr, 2015 1 commit
-
-
Aurel authored
-
- 14 Apr, 2015 7 commits
-
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Xiaowu Zhang authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
Jérome Perrin authored
-
- 10 Apr, 2015 19 commits
-
-
Kazuhiko Shiozaki authored
-
Tristan Cavelier authored
-
Klaus Wölfel authored
-
Klaus Wölfel authored
do not set meaningless contributor category in web page
-
Klaus Wölfel authored
per default it useses indexeddb storage
-
Romain Courteaud authored
Modify jIO API to keep user data not modified. jIO.get({"_id": "foo"} -> jIO.get("foo") jIO.remove({"_id": "foo"} -> jIO.remove("foo") jIO.post({"title": "bar"}) -> jIO.post({"title": "bar"}) jIO.put({"_id": "foo", "title": "bar"}) -> jIO.put("foo", {"title": "bar"}) jIO.getAttachment({"_id": "foo", "_attachment": "enclosure"} -> jIO.getAttachment("foo", "enclosure") jIO.removeAttachment({"_id": "foo", "_attachment": "enclosure"} -> jIO.removeAttachment("foo", "enclosure") jIO.putAttachment({"_id": "foo", "_attachment": "enclosure", "_blob": blob} -> jIO.putAttachment("foo", "enclosure", blob) Add jIO.allAttachments method. jIO.get does not return an _id and _attachments attributes anymore. jIO.get now really returns the document as saved by jIO.put/post.
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Sven Franck authored
-
Jérome Perrin authored
-
- 09 Apr, 2015 1 commit
-
-
Jérome Perrin authored
and in any case, do not accept deleted ones
-
- 07 Apr, 2015 1 commit
-
-
Alain Takoudjou authored
-
- 02 Apr, 2015 1 commit
-
-
Julien Muchembled authored
-
- 01 Apr, 2015 1 commit
-
-
Gabriel Monnerat authored
Because it is breaking the accessors
-
- 31 Mar, 2015 2 commits
-
-
Julien Muchembled authored
Race conditions are likely to happen with CMFActivity between message tables are automatically upgraded during bootstrap. Most code is moved from DA patch to ZMySQLDA.
-
Kazuhiko Shiozaki authored
-
- 30 Mar, 2015 3 commits
-
-
Julien Muchembled authored
-
Gabriel Monnerat authored
-
Julien Muchembled authored
For even more refactoring between SQLDict & SQLQueue, which now uses SQL tables with the same schema.
-
- 27 Mar, 2015 3 commits
-
-
Julien Muchembled authored
The action to recreate activity tables while preserving existing messages was unsafe for 2 reasons: - if any error happened, messages could be lost - it relied on Message.reactivate Which this patch, any instance created after commit d881edd1 (Aug 2010) will upgrade successfully. For older instances, make sure you have no activity left. For cases where 'ALTER TABLE' would not work, a better way to implement repair functionality would be: - one action to backup all messages in ZODB - and another to restore them And maybe a security so that during the backup-clear-restore sequence, activities can't be created nor processed. If any column is added in the future, it would still be possible to write code that fills them by inspecting messages.
-
Julien Muchembled authored
-
Julien Muchembled authored
This is not perfect. There can still be dummy 'MODIFY COLUMN' when the order of columns changes.
-