When a Visual Link is created from one table (source) to another (target), the source table is filtered to reflect selection in the target table.
Assuming there are no selected rows in the target tabale when the visual link is created we see an issue. The server sends a continuous stream of TABLE_ROWS messages to the client, all the same, all with empty data, but with SIZE:0.
There are sent at such a rate that the UI appears unresponsive. If a selection is applied tio target table, it can take upwards of 30 seconds for that selection to take effect, because of the sheer volume of SIZE:0 TABLE_ROW messages being sent and processed.
Soon as the selection does take effect, everything is ok again. If the selection is removed - the spamming starts again.
heswell
commented
4 days ago
When a Visual Link is created from one table (source) to another (target), the source table is filtered to reflect selection in the target table.
Assuming there are no selected rows in the target tabale when the visual link is created we see an issue. The server sends a continuous stream of TABLE_ROWS messages to the client, all the same, all with empty data, but with SIZE:0.
There are sent at such a rate that the UI appears unresponsive. If a selection is applied tio target table, it can take upwards of 30 seconds for that selection to take effect, because of the sheer volume of SIZE:0 TABLE_ROW messages being sent and processed.
Soon as the selection does take effect, everything is ok again. If the selection is removed - the spamming starts again.