Mercurial Mercurial > pub > hg > cubicweb / file revision
summary | shortlog | changelog | graph | tags | bookmarks | branches | files | changeset | file | latest | revisions | annotate | diff | comparison | raw | help
Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
doc/changes/3.23.rst
author Sylvain Thénault <sylvain.thenault@logilab.fr>
Fri, 08 Jul 2016 10:17:14 +0200
changeset 11415 f87da59faea1
parent 11381 750a98450dea
child 11445 b2eb66dfd9c6
permissions -rw-r--r--
[migration] Test and fix case of addition of an attribute with some serialized constraint It was crashing on attempt to remove an unexisting constraint. This code may be removed safely as it's expected to be handled by the constraint removal hook. Notice that adding a vocabulary on shortpara makes yams change the varchar max size. This is arguable but not the point of this test, so simply adapt the max size defined in the schema coherently so we don't have to bother with that at this point.

3.23 (24 June 2016)
===================

New features
------------

* Python 3.x support in CubicWeb itself is now complete, except for the
  twisted package (since Twisted does not completely support Python 3.x
  itself). The skeleton for new cube should also be Python 3 compatible, in
  particular its `setup.py` got updated.

* The `source-sync` command can now synchronize all sources in the database,
  if no `<source>` argument is provided.

* Datafeed source synchronization is now asynchronous when requested from user
  interface.

Database handling
~~~~~~~~~~~~~~~~~

* Most indexes and constraints will be rebuilt during the migration, because
  they are now named after a md5 hash to control the name's size.

* Index are renamed upon renaming of an entity type, so they are still
  correctly tracked.

* A new `db-check-index` command is added to `cubicweb-ctl`, to display the
  differences between the indexes in the database and those expected by the
  schema. It's recommended to run this command after the migration to 3.23 and
  to adjust things manually for cases that are not easily handled by the
  migration script, such as indexes of entity types that have been renamed. It
  should be mostly about dropping extra indexes.


Data-import
~~~~~~~~~~~

* Deprecated `MetaGenerator` in favor of slightly adapted API in
  `MetadataGenerator` (more consistent, giving more control to sub-classes and
  suitable for usage with the `MassiveObjectStore`)

* Major cleanups of the `MassiveObjectStore` and its `PGHelper` companion
  class:

  - dropped a bunch of unnecessary / unused attributes
  - refactored / renamed internal methods
  - added support for a metadata generator, the now recommended way to control
    metadata generation

* Deprecated `SQLGenObjectStore`, `MassiveObjectStore` should be used instead.


Backwards-incompatible changes
------------------------------

* Generative tests *à la logilab-common* are not supported anymore in
  `CubicWebTC`. It is advised to use the subtests_ API (available on
  `CubicWebTC` either from the standard library as of Python 3.4 or through
  unittest2 package otherwise).

* `CubicWebTC`'s `set_description` method (comming from
  `logilab.common.testlib.TestCase`) is no longer available.


.. _subtests: https://docs.python.org/3/library/unittest.html#distinguishing-test-iterations-using-subtests
cubicweb