2020-07-27 18:57:36 +00:00
|
|
|
"""
|
|
|
|
Implements the base classes for Record and RecordSet objects used to represent records in Grist
|
|
|
|
tables. Individual tables use derived versions of these, which add per-column properties.
|
|
|
|
"""
|
|
|
|
|
|
|
|
import functools
|
|
|
|
|
|
|
|
@functools.total_ordering
|
|
|
|
class Record(object):
|
|
|
|
"""
|
|
|
|
Name: Record, rec
|
|
|
|
|
|
|
|
A Record represents a record of data. It is the primary means of accessing values in formulas. A
|
|
|
|
Record for a particular table has a property for each data and formula column in the table.
|
|
|
|
|
|
|
|
In a formula, `$field` is translated to `rec.field`, where `rec` is the Record for which the
|
|
|
|
formula is being evaluated.
|
|
|
|
|
|
|
|
For example:
|
|
|
|
```
|
|
|
|
def Full_Name(rec, table):
|
|
|
|
return rec.First_Name + ' ' + rec.LastName
|
|
|
|
|
|
|
|
def Name_Length(rec, table):
|
|
|
|
return len(rec.Full_Name)
|
|
|
|
```
|
|
|
|
"""
|
|
|
|
|
|
|
|
# Some documentation for method-like parts of Record, which aren't actually methods.
|
|
|
|
_DOC_EXTRA = (
|
|
|
|
"""
|
|
|
|
Name: $Field, rec.Field
|
|
|
|
Usage: __$__*Field* or __rec__*.Field*
|
|
|
|
|
|
|
|
Access the field named "Field" of the current record. E.g. `$First_Name` or `rec.First_Name`.
|
|
|
|
""",
|
|
|
|
"""
|
|
|
|
Name: $group, rec.group
|
|
|
|
Usage: __$group__
|
|
|
|
|
|
|
|
In a summary view, `$group` is a special field containing the list of Records that are
|
|
|
|
summarized by the current summary line. E.g. `len($group)` is the count of those records.
|
|
|
|
|
|
|
|
See [RecordSet](#recordset) for useful properties offered by the returned object.
|
|
|
|
|
|
|
|
Examples:
|
|
|
|
```
|
|
|
|
sum($group.Amount) # Sum of the Amount field in the matching records
|
|
|
|
sum(r.Amount for r in $group) # Same as sum($group.Amount)
|
|
|
|
sum(r.Amount for r in $group if r > 0) # Sum of only the positive amounts
|
|
|
|
sum(r.Shares * r.Price for r in $group) # Sum of shares * price products
|
|
|
|
```
|
|
|
|
"""
|
|
|
|
)
|
|
|
|
|
|
|
|
# Record is always a thin class, containing essentially a reference to a row in the table. The
|
|
|
|
# properties to access individual fields of a row are provided in per-table derived classes.
|
|
|
|
def __init__(self, table, row_id, relation=None):
|
|
|
|
"""
|
|
|
|
Creates a Record object.
|
|
|
|
table - Table object, in which this record lives.
|
|
|
|
row_id - The ID of the record within table.
|
|
|
|
relation - Relation object for how this record was obtained; used in dependency tracking.
|
2021-07-16 18:15:04 +00:00
|
|
|
|
|
|
|
In general you shouldn't call this constructor directly, but rather:
|
|
|
|
|
|
|
|
table.Record(row_id, relation)
|
|
|
|
|
|
|
|
which provides the table argument automatically.
|
2020-07-27 18:57:36 +00:00
|
|
|
"""
|
|
|
|
self._table = table
|
|
|
|
self._row_id = row_id
|
|
|
|
self._source_relation = relation or table._identity_relation
|
|
|
|
|
|
|
|
def _get_col(self, col_id):
|
|
|
|
return self._table._get_col_value(col_id, self._row_id, self._source_relation)
|
|
|
|
|
|
|
|
# Look up a property of the record. Internal properties are simple.
|
|
|
|
# For columns, we explicitly check that we have them before attempting to access.
|
|
|
|
# Otherwise AttributeError is ambiguous - it could be because we don't have the
|
|
|
|
# column, or because the column threw an AttributeError when evaluated.
|
|
|
|
def __getattr__(self, name):
|
|
|
|
if name in self._table.all_columns:
|
|
|
|
return self._get_col(name)
|
|
|
|
return self._table._attribute_error(name, self._source_relation)
|
|
|
|
|
|
|
|
def __hash__(self):
|
|
|
|
return hash((self._table, self._row_id))
|
|
|
|
|
|
|
|
def __eq__(self, other):
|
|
|
|
return (isinstance(other, Record) and
|
|
|
|
(self._table, self._row_id) == (other._table, other._row_id))
|
|
|
|
|
|
|
|
def __ne__(self, other):
|
|
|
|
return not self.__eq__(other)
|
|
|
|
|
|
|
|
def __lt__(self, other):
|
|
|
|
return (self._table.table_id, self._row_id) < (other._table.table_id, other._row_id)
|
|
|
|
|
|
|
|
def __int__(self):
|
|
|
|
return self._row_id
|
|
|
|
|
|
|
|
def __nonzero__(self):
|
|
|
|
return bool(self._row_id)
|
|
|
|
|
2021-06-22 15:12:25 +00:00
|
|
|
__bool__ = __nonzero__
|
|
|
|
|
2020-07-27 18:57:36 +00:00
|
|
|
def __repr__(self):
|
|
|
|
return "%s[%s]" % (self._table.table_id, self._row_id)
|
|
|
|
|
|
|
|
def _clone_with_relation(self, src_relation):
|
2021-07-16 18:15:04 +00:00
|
|
|
return self._table.Record(self._row_id,
|
|
|
|
relation=src_relation.compose(self._source_relation))
|
2020-07-27 18:57:36 +00:00
|
|
|
|
|
|
|
|
|
|
|
class RecordSet(object):
|
|
|
|
"""
|
|
|
|
A RecordSet represents a collection of records, as returned by `Table.lookupRecords()` or
|
|
|
|
`$group` property in summary views.
|
|
|
|
|
|
|
|
A RecordSet allows iterating through the records:
|
|
|
|
```
|
|
|
|
sum(r.Amount for r in Students.lookupRecords(First_Name="John", Last_Name="Doe"))
|
|
|
|
min(r.DueDate for r in Tasks.lookupRecords(Owner="Bob"))
|
|
|
|
```
|
|
|
|
|
|
|
|
RecordSets also provide a convenient way to access the list of values for a particular field for
|
|
|
|
all the records, as `record_set.Field`. For example, the examples above are equivalent to:
|
|
|
|
```
|
|
|
|
sum(Students.lookupRecords(First_Name="John", Last_Name="Doe").Amount)
|
|
|
|
min(Tasks.lookupRecords(Owner="Bob").DueDate)
|
|
|
|
```
|
|
|
|
|
|
|
|
You can get the number of records in a RecordSet using `len`, e.g. `len($group)`.
|
|
|
|
"""
|
|
|
|
def __init__(self, table, row_ids, relation=None, group_by=None, sort_by=None):
|
|
|
|
"""
|
|
|
|
group_by may be a dictionary mapping column names to values that are all the same for the given
|
|
|
|
RecordSet. sort_by may be the column name used for sorting this record set. Both are set by
|
|
|
|
lookupRecords, and used when using RecordSet to insert new records.
|
|
|
|
"""
|
|
|
|
self._table = table
|
|
|
|
self._row_ids = row_ids
|
|
|
|
self._source_relation = relation or table._identity_relation
|
|
|
|
# If row_ids is itself a RecordSet, default to its _group_by and _sort_by properties.
|
|
|
|
self._group_by = group_by or getattr(row_ids, '_group_by', None)
|
|
|
|
self._sort_by = sort_by or getattr(row_ids, '_sort_by', None)
|
|
|
|
|
|
|
|
def __len__(self):
|
|
|
|
return len(self._row_ids)
|
|
|
|
|
|
|
|
def __nonzero__(self):
|
|
|
|
return bool(self._row_ids)
|
|
|
|
|
2021-06-22 15:12:25 +00:00
|
|
|
__bool__ = __nonzero__
|
|
|
|
|
2020-11-02 15:48:47 +00:00
|
|
|
def __eq__(self, other):
|
|
|
|
return (isinstance(other, RecordSet) and
|
(core) Implement trigger formulas (generalizing default formulas)
Summary:
Trigger formulas can be calculated for new records, or for new records and
updates to certain fields, or all fields. They do not recalculate on open,
and they MAY be set directly by the user, including for data-cleaning.
- Column metadata now includes recalcWhen and recalcDeps fields.
- Trigger formulas are NOT recalculated on open or on schema changes.
- When recalcWhen is "never", formula isn't calculated even for new records.
- When recalcWhen is "allupdates", formula is calculated for new records and
any manual (non-formula) updates to the record.
- When recalcWhen is "", formula is calculated for new records, and changes to
recalcDeps fields (which may be formula fields or column itself).
- A column whose recalcDeps includes itself is a "data-cleaning" column; a
value set by the user will still trigger the formula.
- All trigger-formulas receive a "value" argument (to support the case above).
Small changes
- Update RefLists (used for recalcDeps) when target rows are deleted.
- Add RecordList.__contains__ (for `rec in refList` or `id in refList` checks)
- Clarify that Calculate action has replaced load_done() in practice,
and use it in tests too, to better match reality.
Left for later:
- UI for setting recalcWhen / recalcDeps.
- Implementation of actions such as "Recalculate for all cells".
- Allowing trigger-formulas access to the current user's info.
Test Plan: Added a comprehensive python-side test for various trigger combinations
Reviewers: paulfitz, alexmojaki
Reviewed By: paulfitz
Differential Revision: https://phab.getgrist.com/D2872
2021-06-25 20:34:20 +00:00
|
|
|
(self._table, self._row_ids) == (other._table, other._row_ids))
|
2020-11-02 15:48:47 +00:00
|
|
|
|
|
|
|
def __ne__(self, other):
|
|
|
|
return not self.__eq__(other)
|
|
|
|
|
2020-07-27 18:57:36 +00:00
|
|
|
def __iter__(self):
|
|
|
|
for row_id in self._row_ids:
|
2021-07-16 18:15:04 +00:00
|
|
|
yield self._table.Record(row_id, self._source_relation)
|
2020-07-27 18:57:36 +00:00
|
|
|
|
(core) Implement trigger formulas (generalizing default formulas)
Summary:
Trigger formulas can be calculated for new records, or for new records and
updates to certain fields, or all fields. They do not recalculate on open,
and they MAY be set directly by the user, including for data-cleaning.
- Column metadata now includes recalcWhen and recalcDeps fields.
- Trigger formulas are NOT recalculated on open or on schema changes.
- When recalcWhen is "never", formula isn't calculated even for new records.
- When recalcWhen is "allupdates", formula is calculated for new records and
any manual (non-formula) updates to the record.
- When recalcWhen is "", formula is calculated for new records, and changes to
recalcDeps fields (which may be formula fields or column itself).
- A column whose recalcDeps includes itself is a "data-cleaning" column; a
value set by the user will still trigger the formula.
- All trigger-formulas receive a "value" argument (to support the case above).
Small changes
- Update RefLists (used for recalcDeps) when target rows are deleted.
- Add RecordList.__contains__ (for `rec in refList` or `id in refList` checks)
- Clarify that Calculate action has replaced load_done() in practice,
and use it in tests too, to better match reality.
Left for later:
- UI for setting recalcWhen / recalcDeps.
- Implementation of actions such as "Recalculate for all cells".
- Allowing trigger-formulas access to the current user's info.
Test Plan: Added a comprehensive python-side test for various trigger combinations
Reviewers: paulfitz, alexmojaki
Reviewed By: paulfitz
Differential Revision: https://phab.getgrist.com/D2872
2021-06-25 20:34:20 +00:00
|
|
|
def __contains__(self, item):
|
|
|
|
"""item may be a Record or its row_id."""
|
|
|
|
if isinstance(item, int):
|
|
|
|
return item in self._row_ids
|
|
|
|
if isinstance(item, Record) and item._table == self._table:
|
|
|
|
return int(item) in self._row_ids
|
|
|
|
return False
|
|
|
|
|
2020-07-27 18:57:36 +00:00
|
|
|
def get_one(self):
|
|
|
|
row_id = min(self._row_ids) if self._row_ids else 0
|
2021-07-16 18:15:04 +00:00
|
|
|
return self._table.Record(row_id, self._source_relation)
|
2020-07-27 18:57:36 +00:00
|
|
|
|
|
|
|
def _get_col(self, col_id):
|
|
|
|
return self._table._get_col_subset(col_id, self._row_ids, self._source_relation)
|
|
|
|
|
|
|
|
def __getattr__(self, name):
|
|
|
|
if name in self._table.all_columns:
|
|
|
|
return self._get_col(name)
|
|
|
|
return self._table._attribute_error(name, self._source_relation)
|
|
|
|
|
|
|
|
def _clone_with_relation(self, src_relation):
|
2021-07-16 18:15:04 +00:00
|
|
|
return self._table.RecordSet(self._row_ids,
|
|
|
|
relation=src_relation.compose(self._source_relation),
|
|
|
|
group_by=self._group_by,
|
|
|
|
sort_by=self._sort_by)
|
2020-11-02 15:48:47 +00:00
|
|
|
|
|
|
|
|
|
|
|
def adjust_record(relation, value):
|
|
|
|
"""
|
|
|
|
Helper to adjust a Record's source relation to be the composition with the given relation. This
|
|
|
|
is used to wrap values like `foo.bar`: if `bar` is a Record, then its source relation should be
|
|
|
|
the composition of the source relation of `foo` and the relation associated with `bar`.
|
|
|
|
"""
|
|
|
|
if isinstance(value, (Record, RecordSet)):
|
|
|
|
return value._clone_with_relation(relation)
|
|
|
|
return value
|