Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a new column and update it, Data view is not refreshed #5291

Closed
andrewbt opened this issue Aug 28, 2015 · 7 comments

Comments

Projects
None yet
7 participants
@andrewbt
Copy link

commented Aug 28, 2015

Steps to reproduce bug:

  1. In the SQL pane, issue an ALTER TABLE tablename ADD COLUMN newcolumn numeric query. Every row of that new column will be null and will display as such in the Data View.
  2. I want to populate this new column with derivative values from another column (text based percentage strings like "93.45%", I want to make them numeric), so I next issue an UPDATE tablename SET newcolumn = cast(trim(trailing '%' from tablename.textpercentcol) as numeric) query in the SQL pane.
  3. After the query finishes, the Data View still shows every row in my new column as "null". It was only after much wandering around and finally issuing a SELECT * FROM tablename WHERE newcolumn is not null where I realized the update had finally actually occurred and these columns were, in fact, populated.
@andrewbt

This comment has been minimized.

Copy link
Author

commented Aug 28, 2015

Only seems to be the first 40 rows. Might be a caching/CDN problem, but I've hard refreshed the page several times and about 20 minutes has gone past since the first query, so if so our caching isn't updating very fast.

null_column

@andrewbt

This comment has been minimized.

Copy link
Author

commented Aug 28, 2015

Changing the names or datatypes of columns through the UI also runs into the same problem - the changes are not reflected in the UI but have taken place in the database. Refreshing the Data View or waiting a few minutes does not resolve the problem.

@luisbosque

This comment has been minimized.

Copy link
Contributor

commented Sep 15, 2015

Have you tried to run the SELECT query manually to the SQL API? It would be nice trying to run it with v1 and v2 and see if there is any difference in order to check if it's a caching problem or not

@andrewbt

This comment has been minimized.

Copy link
Author

commented Oct 26, 2015

@luisbosque @xavijam I ran into a similar problem with a new dataset (query "alter table add column" but the new column doesn't appear in the Editor; nor does it with the "add column" button) and tested with the SQL API v1 and v2 - the newly-added columns both appear in the API responses. But not the Editor.

@xavijam xavijam modified the milestones: Pozorrubio, La Hinojosa Oct 29, 2015

@d3dc

This comment has been minimized.

Copy link

commented May 12, 2016

Was there any progress on this bug?

We just spent several hours debugging why our named map's interactivity configuration wasn't working, only to notice that our browsers were displaying different column names based on when we first accessed the data view.

Clearing all browser data and relogging seems to have updated the data view. The changes to column names happened 3 days ago.

@kyaroch

This comment has been minimized.

Copy link

commented Jun 8, 2016

I've encountered a problem that may be related. Using the Editor, I renamed a column and created a new column. The changes are visible in SQL queries I run in the Editor, but not visible in the Map View or in the Data View in the absence of a query. I can't edit the renamed column in the GUI, reference it in CartoCSS under either name, or scroll down in the Data View; these all produce error messages.

I was not able to fix this problem by:

  • Refreshing the Editor
  • Logging out and back in again
  • Clearing the browser cache
  • Using a different browser
  • Using a different computer
  • Using a different Internet connection

So far the only solution has been to create a new dataset from a SELECT * FROM table_name query. Apologies if I'm not describing this as clearly as I should be.

@alonsogarciapablo

This comment has been minimized.

Copy link
Contributor

commented Nov 16, 2016

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.