GitLab

Python 3K will only expose iterators.

http://docs.python.org/3.0/whatsnew/3.0.html#views-and-iterators-instead-of-lists

Calling .complete() unconditionnally from the json encoder is unsafe
since on entity creation validation:

* an eid may have been drawn (hence even .has_eid() would not help)
  while processing form data in the edit controller

* a ValidationError may have been raised and the entity-creating
  transaction rollbacked

This leads to a crash on the return path from the validation to the
browser, where the json_dumps((status, args, entity)) call will
stumble upon the .complete() call which will fail because the entity
does not (any more) exist in the database.

--HG--
branch : stable

Make output from __json_encode__ predictable; use it in the ejsonexport
view.

--HG--
branch : stable

This parameter (defaulting to `False`) is used to inform cubicweb that we really
really do not want to cache a value during creation or update. This will be used
by a storage that may do very specific processing on attribute values that result
in a stored value different than the provided one (e.g. BFSS `fs_importing`
mode).

This ``cw_attr_cache`` update is redundant, ``_cw_update_attr_cache`` already do this step.

This follows changesets 552de9f0c46d, 1527b012802f, 25da1e5c7c50 and 4ba11607d84a.

closes #2423719 ?

* when an attribute is listed in dont-cache-attrs, purge any previous value

* test value is actually modified in EditedEntity.__setitem__ before adding
  attribute to dont-cache-attrs

on create_entity, attributes weren't cached, but they are since 4ba11607d84a
and this triggered a bug: used values may be transformed by hooks (e.g.
TidyHtmlFields), ending in invalid value in the cache. This is the regression.

Now, set_attributes used to update the attributes cache while suffering from
the very same pb. This is the now fixed old bug.

Transformed attributes are now recorded in a transaction shared variable, and
those are omitted from the client cache.

Allowing similar usage as create_entity/cw_instantiate.

Update cw code base to remove deprecated calls.

[entity] fix unrelated_rql for creation form vocabulary for relation with specific permissions (closes #2423854)

--HG--
branch : stable

--HG--
branch : stable

--HG--
branch : stable

A new logilab.common.registry module has been created with content from

* cw.vreg (the whole things that was in there)
* cw.appobject (base selectors and all).

In the process, we've done some renaming:

* former selector functions are now known as "predicate", though you still
  use predicates to build an object'selector

* hence `objectify_selector` decorator is now `objectify_predicate`

* the top level registry is now `RegistryStore` (was `VRegistry`)

Also there is no more need for the @lltrace decorator.

On the CubicWeb side, the `selectors` module has been renamed to `predicates`.

There should be full backward compat with proper deprecation warnings.

Formatting, css and js stolen from narval.

notice drop of the .paginable property necessary for 'paginable' affectation as done in the
forthcoming table views refactoring

The view shouldn't crash in such case.
Also refactor xmlrelateditem view and its call on the way.

--HG--
branch : stable

--HG--
branch : stable

[request, ui] printable_value is now a method of request, and may be given dict of formatters to use (closes #1984743)

Json export views are based on the same model as CSV export views.
There are two distinct views :

- *jsonexport* : direct conversion of the result set into json
- *ejsonexport* : convert entities into json

The JSONP parameter is named ``callback`` (same as on geonames, dbepdia
and a lot of sites)

An optional `_indent` request parameter can be passed to pretty print
the results.

[entity] upgrade fetch_[unrelated_]order to benefit from changes introduced in 3.14 (closes #1942758)

of rql generation parts of the ORM now based on rql syntax tree. This allows more powerful and
flexible sort control by giving them the syntax tree instead of manipulating string.

Also:

* prefix new methods by 'cw_'

* fix cases that currently crash in 3.14 due to the refactoring

[datafeed, entities] url for entities from a datafeed source should be on their origin site. Closes #1769391

[ms, entity metas] add 'actual source' to entities table / base entity metadata cache. Closes #1767090

this is needed since for entities from 'copy based sources' such as
datafeed, we want entity.cw_metainformation() to return as 'source'
the datafeed source, not the system source (ie the source where the
entity is actually stored).

For both performance and bootstraping reasons, we should store this
information in the `entities` table and in the _type_source cache.

--HG--
branch : stable

[entity fetch_attrs] remove ambiguous relations on different etypes from fetched attrs or it may produce wrong related results; closes #1700896

--HG--
branch : stable

[entity] fix cw_instantiate w/ reverse_ relation crash when either multiple entities are given or an eid instead of an entity

--HG--
branch : stable

--HG--
branch : oldstable

--HG--
branch : stable

[entity] fix entity fetch_rql when fetch_attrs contains a rtype with multiple destination etypes which do not have the same fetched attributes themselves (closes #1631282)

--HG--
branch : stable

This changeset breaks a number of CW tests, which depends on pre add hooks. I'm
backing it out, so that we can start the need-for-speed sprint with green tests
(and possibly rework this changeset)