# Database Query Browser Edit Button **URL:** \ **Category:** Ignition\ **Tags:** ignition79\ **Created:** [March 11, 2019, 4:58pm UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219 "2019-03-11T16:58:28Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Steve\_Beck](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_beck/32/7813_2.png) [@Steve\_Beck](https://forum.inductiveautomation.com/u/Steve_Beck)\ **Post date:** [March 11, 2019, 4:58pm UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219/1 "2019-03-11T16:58:28Z")
Why is it that for some tables the edit button appears, but on others it’s grayed out? table a: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/f/f87ee2ac7b4bfb390392279cb2a2571c831659e6.png) table b: ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/c96568c2fb9cd2383c7277f63e1171f117b06e13.png) both are select \* from table\_x and both return 10 rows of 6 columns. ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [March 11, 2019, 5:01pm UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219/2 "2019-03-11T17:01:54Z")
The edit button only appears if the table has a primary key (and the JDBC driver recognizes it as a primary key). ---
**Author:** ![Steve\_Beck](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/steve_beck/32/7813_2.png) [@Steve\_Beck](https://forum.inductiveautomation.com/u/Steve_Beck)\ **Post date:** [March 11, 2019, 5:04pm UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219/3 "2019-03-11T17:04:09Z")
Got it, that makes sense now that I think about it. Obviously it wants to use the primary key as the where clause in the update statements that it’s creating. Thank you. ---
**Author:** ![conlonj25](https://avatars.discourse-cdn.com/v4/letter/c/258eb7/32.png) [@conlonj25](https://forum.inductiveautomation.com/u/conlonj25)\ **Post date:** [November 26, 2019, 10:08am UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219/4 "2019-11-26T10:08:30Z")
I’m seeing this in 7.9.10. It seems to be across all tables, including all the system-made ones. I have to manually edit tables using sql or through MySQL workbench. Is there something obvious that I’m missing? Like project permissions or a gateway setting? ---
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [November 26, 2019, 4:25pm UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219/5 "2019-11-26T16:25:39Z")
No, but what does “system-made” tables mean? Not all of the tables generated by Ignition, assuming that’s what that means, actually have primary keys, so I wouldn’t necessarily expect the edit button to work. Nothing else controls whether editing is allowed besides the primary key check. ---
**Author:** ![ht1237](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ht1237/32/12875_2.png) [@ht1237](https://forum.inductiveautomation.com/u/ht1237)\ **Post date:** [January 24, 2020, 6:43pm UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219/6 "2020-01-24T18:43:44Z")
In addition to needing the ID key, it appears that if you have made any WHERE clauses that you will be unable to edit as well. ---
**Author:** ![tyler.bennett](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@tyler.bennett](https://forum.inductiveautomation.com/u/tyler.bennett)\ **Post date:** [February 2, 2026, 7:23pm UTC](https://forum.inductiveautomation.com/t/database-query-browser-edit-button/23219/7 "2026-02-02T19:23:19Z")
Preventing the ability to edit just because the query includes a WHERE clause seems to be an unfortunate decision on the part of IA developers making it a far less useful feature. Why prevent the edit if the primary key exists in the results?