2020-07-27 18:57:36 +00:00
|
|
|
import logger
|
|
|
|
|
|
|
|
import testutil
|
|
|
|
import test_engine
|
|
|
|
from test_engine import Table, Column, View, Section, Field
|
|
|
|
|
|
|
|
log = logger.Logger(__name__, logger.INFO)
|
|
|
|
|
|
|
|
class TestTableActions(test_engine.EngineTestCase):
|
|
|
|
|
|
|
|
address_table_data = [
|
|
|
|
["id", "city", "state", "amount" ],
|
|
|
|
[ 21, "New York", "NY" , 1. ],
|
|
|
|
[ 22, "Albany", "NY" , 2. ],
|
|
|
|
[ 23, "Seattle", "WA" , 3. ],
|
|
|
|
[ 24, "Chicago", "IL" , 4. ],
|
|
|
|
[ 25, "Bedford", "MA" , 5. ],
|
|
|
|
[ 26, "New York", "NY" , 6. ],
|
|
|
|
[ 27, "Buffalo", "NY" , 7. ],
|
|
|
|
[ 28, "Bedford", "NY" , 8. ],
|
|
|
|
[ 29, "Boston", "MA" , 9. ],
|
|
|
|
[ 30, "Yonkers", "NY" , 10. ],
|
|
|
|
[ 31, "New York", "NY" , 11. ],
|
|
|
|
]
|
|
|
|
|
|
|
|
people_table_data = [
|
|
|
|
["id", "name", "address" ],
|
|
|
|
[ 1, "Alice", 22 ],
|
|
|
|
[ 2, "Bob", 25 ],
|
|
|
|
[ 3, "Carol", 27 ],
|
|
|
|
]
|
|
|
|
|
|
|
|
def init_sample_data(self):
|
|
|
|
# Add a couple of tables, including references.
|
|
|
|
self.apply_user_action(["AddTable", "Address", [
|
|
|
|
{"id": "city", "type": "Text"},
|
|
|
|
{"id": "state", "type": "Text"},
|
|
|
|
{"id": "amount", "type": "Numeric"},
|
|
|
|
]])
|
|
|
|
self.apply_user_action(["AddTable", "People", [
|
|
|
|
{"id": "name", "type": "Text"},
|
|
|
|
{"id": "address", "type": "Ref:Address"},
|
|
|
|
{"id": "city", "type": "Any", "formula": "$address.city" }
|
|
|
|
]])
|
|
|
|
|
|
|
|
# Populate some data.
|
|
|
|
d = testutil.table_data_from_rows("Address", self.address_table_data[0],
|
|
|
|
self.address_table_data[1:])
|
|
|
|
self.apply_user_action(["BulkAddRecord", "Address", d.row_ids, d.columns])
|
|
|
|
|
|
|
|
d = testutil.table_data_from_rows("People", self.people_table_data[0],
|
|
|
|
self.people_table_data[1:])
|
|
|
|
self.apply_user_action(["BulkAddRecord", "People", d.row_ids, d.columns])
|
|
|
|
|
|
|
|
# Add a view with several sections, including a summary table.
|
2022-05-04 09:54:30 +00:00
|
|
|
self.apply_user_action(["CreateViewSection", 1, 0, 'record', None, None])
|
|
|
|
self.apply_user_action(["CreateViewSection", 1, 3, 'record', [3], None])
|
|
|
|
self.apply_user_action(["CreateViewSection", 2, 3, 'record', None, None])
|
2020-07-27 18:57:36 +00:00
|
|
|
|
|
|
|
# Verify the new structure of tables and views.
|
|
|
|
self.assertTables([
|
|
|
|
Table(1, "Address", primaryViewId=1, summarySourceTable=0, columns=[
|
|
|
|
Column(1, "manualSort", "ManualSortPos", False, "", 0),
|
|
|
|
Column(2, "city", "Text", False, "", 0),
|
|
|
|
Column(3, "state", "Text", False, "", 0),
|
|
|
|
Column(4, "amount", "Numeric", False, "", 0),
|
|
|
|
]),
|
|
|
|
Table(2, "People", primaryViewId=2, summarySourceTable=0, columns=[
|
|
|
|
Column(5, "manualSort", "ManualSortPos", False, "", 0),
|
|
|
|
Column(6, "name", "Text", False, "", 0),
|
|
|
|
Column(7, "address", "Ref:Address", False, "", 0),
|
|
|
|
Column(8, "city", "Any", True, "$address.city", 0),
|
|
|
|
]),
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
Table(3, "Address_summary_state", 0, 1, columns=[
|
2020-07-27 18:57:36 +00:00
|
|
|
Column(9, "state", "Text", False, "", summarySourceCol=3),
|
|
|
|
Column(10, "group", "RefList:Address", True, summarySourceCol=0,
|
|
|
|
formula="table.getSummarySourceGroup(rec)"),
|
|
|
|
Column(11, "count", "Int", True, summarySourceCol=0, formula="len($group)"),
|
|
|
|
Column(12, "amount", "Numeric", True, summarySourceCol=0, formula="SUM($group.amount)"),
|
|
|
|
]),
|
|
|
|
])
|
|
|
|
self.assertViews([
|
|
|
|
View(1, sections=[
|
|
|
|
Section(1, parentKey="record", tableRef=1, fields=[
|
|
|
|
Field(1, colRef=2),
|
|
|
|
Field(2, colRef=3),
|
|
|
|
Field(3, colRef=4),
|
|
|
|
]),
|
|
|
|
]),
|
|
|
|
View(2, sections=[
|
2022-02-01 18:48:39 +00:00
|
|
|
Section(3, parentKey="record", tableRef=2, fields=[
|
|
|
|
Field(7, colRef=6),
|
|
|
|
Field(8, colRef=7),
|
|
|
|
Field(9, colRef=8),
|
2020-07-27 18:57:36 +00:00
|
|
|
]),
|
|
|
|
]),
|
|
|
|
View(3, sections=[
|
2022-02-01 18:48:39 +00:00
|
|
|
Section(5, parentKey="record", tableRef=1, fields=[
|
|
|
|
Field(13, colRef=2),
|
|
|
|
Field(14, colRef=3),
|
|
|
|
Field(15, colRef=4),
|
2020-07-27 18:57:36 +00:00
|
|
|
]),
|
2022-07-06 07:41:09 +00:00
|
|
|
Section(7, parentKey="record", tableRef=3, fields=[
|
|
|
|
Field(19, colRef=9),
|
|
|
|
Field(20, colRef=11),
|
|
|
|
Field(21, colRef=12),
|
2020-07-27 18:57:36 +00:00
|
|
|
]),
|
2022-07-06 07:41:09 +00:00
|
|
|
Section(8, parentKey="record", tableRef=2, fields=[
|
|
|
|
Field(22, colRef=6),
|
|
|
|
Field(23, colRef=7),
|
|
|
|
Field(24, colRef=8),
|
2020-07-27 18:57:36 +00:00
|
|
|
]),
|
|
|
|
]),
|
|
|
|
])
|
|
|
|
|
|
|
|
# Verify the data we've loaded.
|
|
|
|
self.assertTableData('Address', cols="subset", data=self.address_table_data)
|
|
|
|
self.assertTableData('People', cols="subset", data=self.people_table_data)
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
self.assertTableData("Address_summary_state", cols="subset", data=[
|
2020-07-27 18:57:36 +00:00
|
|
|
[ "id", "state", "count", "amount" ],
|
|
|
|
[ 1, "NY", 7, 1.+2+6+7+8+10+11 ],
|
|
|
|
[ 2, "WA", 1, 3. ],
|
|
|
|
[ 3, "IL", 1, 4. ],
|
|
|
|
[ 4, "MA", 2, 5.+9 ],
|
|
|
|
])
|
|
|
|
|
|
|
|
#----------------------------------------------------------------------
|
|
|
|
|
|
|
|
@test_engine.test_undo
|
|
|
|
def test_table_updates(self):
|
|
|
|
# Verify table renames triggered by UpdateRecord actions, and related behavior.
|
|
|
|
|
|
|
|
# Load a sample with a few table and views.
|
|
|
|
self.init_sample_data()
|
|
|
|
|
|
|
|
# Verify that we can rename tables via UpdatRecord actions, including multiple tables.
|
|
|
|
self.apply_user_action(["BulkUpdateRecord", "_grist_Tables", [1,2],
|
|
|
|
{"tableId": ["Location", "Persons"]}])
|
|
|
|
|
|
|
|
# Check that requested tables and summary tables got renamed correctly.
|
|
|
|
self.assertTableData('_grist_Tables', cols="subset", data=[
|
|
|
|
["id", "tableId"],
|
|
|
|
[1, "Location"],
|
|
|
|
[2, "Persons"],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
[3, "Location_summary_state"],
|
2020-07-27 18:57:36 +00:00
|
|
|
])
|
|
|
|
|
|
|
|
# Check that reference columns to renamed tables get their type modified.
|
|
|
|
self.assertTableData('_grist_Tables_column', rows="subset", cols="subset", data=[
|
|
|
|
["id", "colId", "type"],
|
|
|
|
[7, "address", "Ref:Location"],
|
|
|
|
[10, "group", "RefList:Location"],
|
|
|
|
])
|
|
|
|
|
|
|
|
# Do a bulk update to rename A and B to conflicting names.
|
|
|
|
self.apply_user_action(["AddTable", "A", [{"id": "a", "type": "Text"}]])
|
|
|
|
out_actions = self.apply_user_action(["BulkUpdateRecord", "_grist_Tables", [1,2],
|
|
|
|
{"tableId": ["A", "A"]}])
|
|
|
|
|
|
|
|
# See what doc-actions get generated.
|
|
|
|
self.assertPartialOutActions(out_actions, {
|
|
|
|
"stored": [
|
|
|
|
["ModifyColumn", "Persons", "address", {"type": "Int"}],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
["ModifyColumn", "Location_summary_state", "group", {"type": "Int"}],
|
2020-07-27 18:57:36 +00:00
|
|
|
["RenameTable", "Location", "A2"],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
["RenameTable", "Location_summary_state", "A2_summary_state"],
|
2020-07-27 18:57:36 +00:00
|
|
|
["RenameTable", "Persons", "A3"],
|
|
|
|
["BulkUpdateRecord", "_grist_Tables", [1, 3, 2],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
{"tableId": ["A2", "A2_summary_state", "A3"]}],
|
2020-07-27 18:57:36 +00:00
|
|
|
["ModifyColumn", "A3", "address", {"type": "Ref:A2"}],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
["ModifyColumn", "A2_summary_state", "group", {"type": "RefList:A2"}],
|
2020-07-27 18:57:36 +00:00
|
|
|
["BulkUpdateRecord", "_grist_Tables_column", [7, 10], {"type": ["Ref:A2", "RefList:A2"]}],
|
|
|
|
]
|
|
|
|
})
|
|
|
|
|
|
|
|
# Check that requested tables and summary tables got renamed correctly.
|
|
|
|
self.assertTableData('_grist_Tables', cols="subset", data=[
|
|
|
|
["id", "tableId"],
|
|
|
|
[1, "A2"],
|
|
|
|
[2, "A3"],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
[3, "A2_summary_state"],
|
2020-07-27 18:57:36 +00:00
|
|
|
[4, "A"],
|
|
|
|
])
|
|
|
|
|
|
|
|
# Check that reference columns to renamed tables get their type modified.
|
|
|
|
self.assertTableData('_grist_Tables_column', rows="subset", cols="subset", data=[
|
|
|
|
["id", "colId", "type"],
|
|
|
|
[7, "address", "Ref:A2"],
|
|
|
|
[10, "group", "RefList:A2"],
|
|
|
|
])
|
|
|
|
|
|
|
|
# Verify the data we've loaded.
|
|
|
|
self.assertTableData('A2', cols="subset", data=self.address_table_data)
|
|
|
|
self.assertTableData('A3', cols="subset", data=self.people_table_data)
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
self.assertTableData("A2_summary_state", cols="subset", data=[
|
2020-07-27 18:57:36 +00:00
|
|
|
[ "id", "state", "count", "amount" ],
|
|
|
|
[ 1, "NY", 7, 1.+2+6+7+8+10+11 ],
|
|
|
|
[ 2, "WA", 1, 3. ],
|
|
|
|
[ 3, "IL", 1, 4. ],
|
|
|
|
[ 4, "MA", 2, 5.+9 ],
|
|
|
|
])
|
|
|
|
|
|
|
|
#----------------------------------------------------------------------
|
|
|
|
|
|
|
|
@test_engine.test_undo
|
|
|
|
def test_table_renames_summary_by_ref(self):
|
|
|
|
# Verify table renames when there is a group-by column that's a Reference.
|
|
|
|
|
|
|
|
# This tests a potential bug since a table rename needs to modify Reference types, but
|
|
|
|
# group-by columns aren't supposed to be modifiable.
|
|
|
|
self.init_sample_data()
|
|
|
|
|
|
|
|
# Add a table grouped by a reference column (the 'Ref:Address' column named 'address').
|
2022-05-04 09:54:30 +00:00
|
|
|
self.apply_user_action(["CreateViewSection", 2, 0, 'record', [7], None])
|
2020-07-27 18:57:36 +00:00
|
|
|
self.assertTableData('_grist_Tables_column', cols="subset", data=[
|
|
|
|
["id", "colId", "type", "isFormula", "formula" ],
|
|
|
|
[ 13, "address", "Ref:Address", False, "" ],
|
|
|
|
[ 14, "group", "RefList:People", True, "table.getSummarySourceGroup(rec)" ],
|
|
|
|
[ 15, "count", "Int", True, "len($group)" ],
|
|
|
|
], rows=lambda r: (r.parentId.id == 4))
|
|
|
|
|
|
|
|
# Now rename the table Address -> Location.
|
|
|
|
out_actions = self.apply_user_action(["RenameTable", "Address", "Location"])
|
|
|
|
|
|
|
|
# See what doc-actions get generated.
|
|
|
|
self.assertPartialOutActions(out_actions, {
|
|
|
|
"stored": [
|
|
|
|
["ModifyColumn", "People", "address", {"type": "Int"}],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
["ModifyColumn", "Address_summary_state", "group", {"type": "Int"}],
|
|
|
|
["ModifyColumn", "People_summary_address", "address", {"type": "Int"}],
|
2020-07-27 18:57:36 +00:00
|
|
|
["RenameTable", "Address", "Location"],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
["RenameTable", "Address_summary_state", "Location_summary_state"],
|
2020-07-27 18:57:36 +00:00
|
|
|
["BulkUpdateRecord", "_grist_Tables", [1, 3],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
{"tableId": ["Location", "Location_summary_state"]}],
|
2020-07-27 18:57:36 +00:00
|
|
|
["ModifyColumn", "People", "address", {"type": "Ref:Location"}],
|
(core) Nice summary table IDs
Summary:
Changes auto-generated summary table IDs from e.g. `GristSummary_6_Table1` to `Table1_summary_A_B` (meaning `Table1` grouped by `A` and `B`). This makes it easier to write formulas involving summary tables, make API requests, understand logs, etc.
Because these don't encode the source table ID as reliably as before, `decode_summary_table_name` now uses the summary table schema info, not just the summary table ID. Specifically, it looks at the type of the `group` column, which is `RefList:<source table id>`.
Renaming a source table renames the summary table as before, and now renaming a groupby column renames the summary table as well.
Conflicting table names are resolved in the usual way by adding a number at the end, e.g. `Table1_summary_A_B2`. These summary tables are not automatically renamed when the disambiguation is no longer needed.
A new migration renames all summary tables to the new scheme, and updates formulas using summary tables with a simple regex.
Test Plan:
Updated many tests to use the new style of name.
Added new Python tests to for resolving conflicts when renaming source tables and groupby columns.
Added a test for the migration, including renames in formulas.
Reviewers: georgegevoian
Reviewed By: georgegevoian
Differential Revision: https://phab.getgrist.com/D3508
2022-07-11 18:00:25 +00:00
|
|
|
["ModifyColumn", "Location_summary_state", "group", {"type": "RefList:Location"}],
|
|
|
|
["ModifyColumn", "People_summary_address", "address", {"type": "Ref:Location"}],
|
2020-07-27 18:57:36 +00:00
|
|
|
["BulkUpdateRecord", "_grist_Tables_column", [7, 10, 13],
|
|
|
|
{"type": ["Ref:Location", "RefList:Location", "Ref:Location"]}],
|
|
|
|
]
|
|
|
|
})
|
|
|
|
|
|
|
|
self.assertTableData('_grist_Tables_column', cols="subset", data=[
|
|
|
|
["id", "colId", "type", "isFormula", "formula" ],
|
|
|
|
[ 13, "address", "Ref:Location", False, "" ],
|
|
|
|
[ 14, "group", "RefList:People", True, "table.getSummarySourceGroup(rec)" ],
|
|
|
|
[ 15, "count", "Int", True, "len($group)" ],
|
|
|
|
], rows=lambda r: (r.parentId.id == 4))
|
|
|
|
|
|
|
|
|
|
|
|
#----------------------------------------------------------------------
|
|
|
|
|
|
|
|
@test_engine.test_undo
|
|
|
|
def test_table_removes(self):
|
|
|
|
# Verify table removals triggered by UpdateRecord actions, and related behavior.
|
|
|
|
|
|
|
|
# Same setup as previous test.
|
|
|
|
self.init_sample_data()
|
|
|
|
|
|
|
|
# Add one more table, and one more view for tables #1 and #4 (those we are about to delete).
|
2022-05-04 09:54:30 +00:00
|
|
|
self.apply_user_action(["AddEmptyTable", None])
|
|
|
|
out_actions = self.apply_user_action(["CreateViewSection", 1, 0, 'detail', None, None])
|
2020-07-27 18:57:36 +00:00
|
|
|
self.assertEqual(out_actions.retValues[0]["viewRef"], 5)
|
2022-05-04 09:54:30 +00:00
|
|
|
self.apply_user_action(["CreateViewSection", 4, 5, 'detail', None, None])
|
2020-07-27 18:57:36 +00:00
|
|
|
|
2021-11-30 17:46:21 +00:00
|
|
|
# See what's in TabBar table, to verify after we remove a table.
|
2020-07-27 18:57:36 +00:00
|
|
|
self.assertTableData('_grist_TabBar', cols="subset", data=[
|
|
|
|
["id", "viewRef"],
|
|
|
|
[1, 1],
|
|
|
|
[2, 2],
|
|
|
|
[3, 3],
|
|
|
|
[4, 4],
|
|
|
|
[5, 5],
|
|
|
|
])
|
|
|
|
|
|
|
|
# Remove two tables, ensure certain views get removed.
|
|
|
|
self.apply_user_action(["BulkRemoveRecord", "_grist_Tables", [1, 4]])
|
|
|
|
|
2021-11-30 17:46:21 +00:00
|
|
|
# See that some TabBar entries disappear, or tableRef gets unset.
|
2020-07-27 18:57:36 +00:00
|
|
|
self.assertTableData('_grist_TabBar', cols="subset", data=[
|
|
|
|
["id", "viewRef"],
|
|
|
|
[2, 2],
|
|
|
|
[3, 3],
|
|
|
|
])
|
|
|
|
|
|
|
|
# Check that reference columns to this table get removed, with associated fields.
|
|
|
|
self.assertTables([
|
|
|
|
Table(2, "People", primaryViewId=2, summarySourceTable=0, columns=[
|
|
|
|
Column(5, "manualSort", "ManualSortPos", False, "", 0),
|
|
|
|
Column(6, "name", "Text", False, "", 0),
|
|
|
|
Column(8, "city", "Any", True, "$address.city", 0),
|
|
|
|
]),
|
|
|
|
# Note that the summary table is also gone.
|
|
|
|
])
|
|
|
|
self.assertViews([
|
|
|
|
View(2, sections=[
|
2022-02-01 18:48:39 +00:00
|
|
|
Section(3, parentKey="record", tableRef=2, fields=[
|
|
|
|
Field(7, colRef=6),
|
|
|
|
Field(9, colRef=8),
|
2020-07-27 18:57:36 +00:00
|
|
|
]),
|
|
|
|
]),
|
|
|
|
View(3, sections=[
|
2022-07-06 07:41:09 +00:00
|
|
|
Section(8, parentKey="record", tableRef=2, fields=[
|
|
|
|
Field(22, colRef=6),
|
|
|
|
Field(24, colRef=8),
|
2020-07-27 18:57:36 +00:00
|
|
|
]),
|
|
|
|
]),
|
|
|
|
])
|