Cédric Krier 92d8d29fad Do not instantiate reference field with negative id ...

The reference fields can have a negative id if no record was selected on the
client. It is not expected to get such temporary instance from a reference
field on a saved record.

issue6091
review26941002

2016-12-16 11:00:04 +01:00

..

fields

Remove support for simplejson

2016-11-05 19:54:12 +01:00

__init__.py

Add sequence_ordered

2016-09-13 14:01:17 +02:00

descriptors.py

Use dualmethod on ModelStorage.save

2014-11-01 11:52:55 +01:00

dictschema.py

Remove support for simplejson

2016-11-05 19:54:12 +01:00

match.py

Add MachMixin

2014-05-09 23:16:19 +02:00

model.py

Use 'default_rec_name' context key in Model.default_get

2016-08-04 23:54:50 +02:00

modelsingleton.py

Only return default record if no domain supplied on ModelSingleton search

2015-06-15 10:19:01 +02:00

modelsql.py

Use original transaction to check created/deleted records in __raise_integrity_error

2016-11-28 00:01:51 +01:00

modelstorage.py

Do not instantiate reference field with negative id

2016-12-16 11:00:04 +01:00

modelview.py

Allow to define the text color and background color in calendar view

2016-10-28 17:55:09 +02:00

order.py

Add sequence_ordered

2016-09-13 14:01:17 +02:00

union.py

Add name to union_column to ease override

2014-06-22 17:11:06 +02:00

workflow.py

Re-introduce iteration over keys

2016-03-19 15:25:49 +01:00