You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Updating queries with different numbers and names of columns #507
Try the following scenario from Falcon with an SQL connector like Postgres:
Create a query select 1 as a and save it. The result is as expected.
Update it to select 2 as a and save it. The result is as expected.
Update it to select 3 as b and save it. Note that the grid on the Plotly side still has the column named a and not b although the cell value in the row is indeed 3 and the metadata did get updated.
Update it to select 3 as a, 4 as c and note the pattern: still 1 column only.
Update it to select 3 and note the JSON error without indication of which processing-stage it came from.
A different set of examples is possible when the original dataset has more than 1 column and we try to update it with a dataset with fewer columns: more errors.
These errors don't appear in the webapp-based UI, presumably because it has a different set of API calls when registering a query change, which re-registers the columns?
Heads-up @scjody, this is likely a new blocker for 2.5.0.
FWIW I would consider just raising a user-visible error in cases like this, so that we can move forward with the release, if it's not feasible to actually resolve this fully/properly within the next few days.
Activity
scjody commentedon Aug 4, 2018
@nicolaskruchten Is this a regression from 2.4.0? If so can you log an issue in streambed so we can add it to the project?
nicolaskruchten commentedon Aug 6, 2018
Looks like this issues is known, in the code/logs at any rate: https://github.com/plotly/falcon-sql-client/blob/9e5badbb502e88295bd1fac60da2929e5dce3599/backend/persistent/plotly-api.js#L171
nicolaskruchten commentedon Aug 6, 2018
FWIW I would consider just raising a user-visible error in cases like this, so that we can move forward with the release, if it's not feasible to actually resolve this fully/properly within the next few days.
nicolaskruchten commentedon Aug 10, 2018
Closed by #511