[inlined form field] fix regression introduced in 3.16.4/570208f74a84. Closes #3064653 In the above changeset, we changed ordered entities to be edited according to mandatory inlined constraints, though this leads to unpredictable order in cases where there are no constraint. This leads to case where inlined relation field may think there is no value related to a mandatory relation, while this is simply because there is a value specified but to an entity that will be created later (together with the relation). To fix this, we've to use the fact that the RelationField.process_form_value return None in cases where there is some entity to be created, while an empty set when there are no linked entity. The new no_value() method allows to differentiate between those different notion of 'no-value'.

     1

.TH cubicweb\-ctl 1 "2010-01-14" cubicweb\-ctl

     2

.SH NAME

     3

.B cubicweb\-ctl

     4

\- cubicweb control utility

     5

     6

     7

.SH SYNOPSIS

     8

.B  cubicweb-ctl <command>

     9

[

    10

.I OPTIONS

    11

] [

    12

.I <command arguments>

    13

]

    14

    15

.SH DESCRIPTION

    16

.PP

    17

CubicWeb utility to create and control instances, and more generally do all

    18

cubicweb's related tasks you can have to do using the command line. Available

    19

commands will depends on which part of the framework are installed.

    20

.PP

    21

Type

    22

.B "cubicweb\-ctl <command> \fB\-\-help\fR"

    23

for more information about a specific command.

    24

    25

.SH COPYRIGHT 

    26

Copyright (c) 2003-2010 LOGILAB S.A. (Paris, FRANCE).

    27

http://www.logilab.fr/ -- mailto:contact@logilab.fr