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
There has been some conversations about this type of capability. Fundamentally there is nothing stopping us from doing this, with the possible exception that this, by definition, is a subset of functionality already available with SQL functions - so we need to clearly understand why we want to duplicate it... that said, this is indeed simpler than writing a full sql function. This also requires some somewhat unsafe SQL manipulation, but nothing too dangerous - i.e. config author can now write DROP TABLE in that statement, but i guess we have to trust config file.
I don't think we want the second table_sql variant, as it creates more problems -- we would need to evaluate the statement, see which columns are returned, check that exactly one of them is a gis column, match it up with the rest of the table configuration, ... - not worth it. Adding where config value on the other hand seems like a good path.
In short - PRs welcome, should be fairly simple to add.
That would be very useful to have "where" in table sources:
The text was updated successfully, but these errors were encountered: