Bug #50705 | No "Edit Table" option in SQL Editor interface | ||
---|---|---|---|
Submitted: | 29 Jan 2010 0:54 | Modified: | 2 Feb 2010 15:25 |
Reporter: | Steve Miller | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 5.2.15 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | editor, query, SQL, table |
[29 Jan 2010 0:54]
Steve Miller
[29 Jan 2010 21:50]
Johannes Taxacher
We chose this for WB over the solution in QB because for a recordset to be editable, it needs to contain the PK columns. if thats not the case, updates can not be applied to the db. In QB we had some tricky query manipulation that added the PK columns invisibly to the query - but that raised a couple of other complications, so we didn't want to keep that solution in WB. The artificial EDIT statement can also be used in combination with an WHERE clause, so one can filter the data for editing. We will add a comment to the generated edit code to visualize this functionality.
[29 Jan 2010 23:03]
Johannes Taxacher
comments have been added to the EDIT statement. will be included in 5.2.16
[2 Feb 2010 15:25]
Tony Bedford
An entry has been added to the 5.2.16 changelog: In the SQL Editor a comment has been added to the EDIT statement to clarify its functionality.