CHANGES 1.29 KB
Newer Older
Julien Muchembled's avatar
Julien Muchembled committed
1 2 3
Change History
==============

4 5 6 7 8
1.0 (unreleased)
----------------

- Drop compatibility with Python < 2.6 and ZODB < 3.9

Julien Muchembled's avatar
Julien Muchembled committed
9
0.10 (2011-10-17)
10 11
-----------------

12 13
- Storage was unable or slow to process large-sized transactions.
  This required to change protocol and MySQL tables format.
14 15 16
- NEO learned to store empty values (although it's useless when managed by
  a ZODB Connection).

Julien Muchembled's avatar
Julien Muchembled committed
17
0.9.2 (2011-10-17)
18 19
------------------

20 21
- storage: a specific socket can be given to MySQL backend
- storage: a ConflictError could happen when client is much faster than master
22
- 'verbose' command line option of 'neomigrate' did not work
23
- client: ZODB monkey-patch randomly raised a NameError
24

Julien Muchembled's avatar
Julien Muchembled committed
25
0.9.1 (2011-09-24)
Julien Muchembled's avatar
Julien Muchembled committed
26 27 28 29 30 31 32 33
------------------

- client: method to retrieve history of persistent objects was incompatible
  with recent ZODB and needlessly asked all storages systematically.
- neoctl: 'print node' command (to get list of all nodes) raised an
  AssertionError.
- 'neomigrate' raised a TypeError when converting NEO DB back to FileStorage.

Julien Muchembled's avatar
Julien Muchembled committed
34 35 36 37 38 39 40 41 42 43 44
0.9 (2011-09-12)
----------------

Initial release.

NEO is considered stable enough to replace existing ZEO setups, except that:

- there's no backup mechanism (aka efficient snapshoting): there's only
  replication and underlying MySQL tools

- MySQL tables format may change in the future