Suggestions for the next realease - 11/23/23 02:23 PM
-When double clicking on a word the cursor flashes in the middle of the word, you can't know if the word is selected
-- The pinned option in this version is horrible. In this new realease, the pinned was placed, I expected it to be the same as the pl/sql developer. The grid should only be pinned if you right-click on the grid and put it pinned (the same as the pl/sql developer)
most important: When executing a query the grid is assembled, if you execute another different query another grid is assembled. When you place the cursor on query 1, its grid is displayed and if you place the cursor on query 2, the grid for query 2 is displayed.
If 10 queries fail, 10 grids will be created
In my opinion: If executing query 1 displays its grid, and if executing query 2 destroys the grid of query 1 and presents the grid to query 2, the grids are never in memory.
The grid presents a certain number of lines. Press the fetch button to go to the end of the query result
-- The pinned option in this version is horrible. In this new realease, the pinned was placed, I expected it to be the same as the pl/sql developer. The grid should only be pinned if you right-click on the grid and put it pinned (the same as the pl/sql developer)
most important: When executing a query the grid is assembled, if you execute another different query another grid is assembled. When you place the cursor on query 1, its grid is displayed and if you place the cursor on query 2, the grid for query 2 is displayed.
If 10 queries fail, 10 grids will be created
In my opinion: If executing query 1 displays its grid, and if executing query 2 destroys the grid of query 1 and presents the grid to query 2, the grids are never in memory.
The grid presents a certain number of lines. Press the fetch button to go to the end of the query result