expdatasyncconflict
Available since Exponential 6.0.15 (in development, not in a release yet).
Summary
A conflict of a two-way synchronisation with the rule "ask" (table exp_data_sync_conflict): both sides changed since the last synchronisation; the values of both are kept until someone takes one in the administration.
Description
A conflict of a two-way synchronisation with the rule "ask" (table exp_data_sync_conflict): both sides changed since the last synchronisation; the values of both are kept until someone takes one in the administration.
@since 6.0.15
Persistent
Yes. Table exp_data_sync_conflict.
Attributes
| Attribute | Type | Static* |
|---|---|---|
| id | integer | Yes. |
| sync_id | integer | Yes. |
| link_id | integer | Yes. |
| object_id | integer | Yes. |
| row_key | string | Yes. |
| content_values | text | Yes. |
| row_values | text | Yes. |
| detected | integer | Yes. |
| state | string | Yes. |
| resolution | string | Yes. |
| resolved | integer | Yes. |
| resolver_id | integer | Yes. |
| content_array | - | No. |
| row_array | - | No. |
| differences | - | No. |
* Yes: a field of the table (a stored value); No: a function attribute, computed when it is asked for.
Source
kernel/classes/datatable/sync/expdatasyncdefinition.php, expDataSyncConflict::definition()
Added to the reference for Exponential 6.0.15: the 4.x reference had no page for this object.
Contributors
- Graham Brookins Updated
Comments
Add a comment