Why a non-read-omly connection tables can't be edited? Follow Answered Dawid Created July 05, 2022 09:18 Sometimes they can, sometimes they can't Same table but when data is shows not in Services but in the Console tab
Have you noticed any patterns to reproduce that problem?
Action will not be available if there is an introspection or indexing process running (you can check the right-bottom bar for these actions).
How can I stop the introspection? Sometimes it takes dozens of minutes but I think that could be the reason actually. But if the introspection is in a different portion of the database, why would it still lock this one table?
Also the difference in my screenshots is in matter of seconds and the one in services tab actually didn't get enabled even after a while
Please share the information about your connection by clicking on Test Connection button in the data source properties.
I cannot reproduce the problem with a disabled button for adding a new row in Services tab.
Feel free to follow DBE-6687 to support introspection for specified/selected objects. I believe it will speed up the process in your case.
@Dawid, is that tables (result sets) produced by a query?
Yes the result is always produced by the query
Could you provide sample query? Since we've numerous issues similar to yours and I hope we can find root cause together.
Or you could find similar issue from the list:
The query was just a simple SELECT * FROM table, no JOINs (as I know sometimes joins render the result read-only)
Strange, could you add any rows to that table if you open it from Database Navigator via F4?