You should be able to edit your data in this mode

[xavijam]

JIRA ref: https://cartodb.atlassian.net/browse/CDB-238

[xavijam]

cc @javierarce

[gouldingken]

It appears that 'Filter mode' is basically just modifying the SQL query. Could you make a special case to enable editing for all queries which start with "SELECT * from current_carto_db_table".

[strk]

Is this still an issue ? Last update was 4 months ago

[saleiva]

Yeah. In afraid yes. Can someone take a look if its on JIRA? I cannot check it now

Sent from my iPhone

On 11/09/2013, at 13:23, strk notifications@github.com wrote:

Is this still an issue ? Last update was 4 months ago

—
Reply to this email directly or view it on GitHub.

[javisantana]

it's already open

[strk]

https://cartodb.atlassian.net/browse/CDB-238

[iriberri]

Hey, one year and 1000 tickets after this, let's solve it! :) @Xatpy

[Xatpy]

Yes! It is being requested from support:

If a query/filter is applied to the table, the listing are no longer editable. Is there an out-of-the-box solution for searching for a listing and then editing in CartoDB? Any suggestions that I could pass on to my clients?

[gagecarto]

I'd love to see this feature! CartoDB rocks!

[Xatpy]

We have just received another ticket about it (SB / 3432212).

[pkej]

Hi,
I guess it is my support ticket you refer to, Xatpy. I'd like to stress that we have 48 000+ long table, which is just for one of three territories which are of interest for us, I'm awaiting a doubling of our database when it comes to names, though I might prune it for non-Sami-language place names.

[iriberri]

One more time, we've just been asked about this again. 😄

[iriberri]

One more time! @saleiva push? :)

[ztephm]

Hi, another user asking for this, S/B: 5454984
cc @jsantana

[iriberri]

@javisantana what do you think?

[alonsogarciapablo]

There's something that still needs to be done. This how it's working right now:

As a result of this, the UI is a bit inconsistent because the filters haven't been refreshed/updated and we're still seeing a row that shouldn't be there according to the filters. I think a good solution would be to update the filters so that it shows the new value and "enable" it so that the row is not removed from the table.

[saleiva]

+1

[xavijam]

Agree

[iriberri]

Mola, and 👍

[alonsogarciapablo]

This is now working very good with discrete filters (on string columns):

I found a problem with regular filters (numbers and columns) and I'm working on fixing that now.

[xavijam]

Super duper!