|
BAREFEET The improvements look great :-) Some feedback on your feedback ;-) : 1. RazorSQL now recognizing SQLite's rowid column for updates/deletes looks great. We can edit tables now that use the rowid implicit primary key. If there is an explicit primary key, however, I think RazorSQL should default to using that key and not rowid. At present it uses both, which seems redundant (eg executes WHERE rowid = 120 AND ID = 120). And if rowid is already present in a view, RazorSQL shouldn't add yet another copy of it. 2. Tabbing through a row (from column to column) now works nicely. 3. The pop up menu option to "Edit Table" is a welcome more direct method. Perhaps better still would be for double clicking on the table/view. Double click in the entity browser currently just does the same as clicking the expansion triangle so would be better utilized. 4&6. Nulls now show as empty cells in the query results pane (great), but not in the edit window (show as "null"), which makes it look cluttered. Admittedly you'd need some way to show and enter null as distinct from empty cells when editing. Perhaps something less obtrusive than the word "null", or a reference on what to show. Presumably a text entry of the literal word "null" currently appears the same as a null, so it is currently ambiguous anyway. 5. I confirmed that RazorSQL does enter integers into an integer column in a table, thank you. It is not true that "SQLite views are read-only". SQLite uses "instead of" triggers to redirect update/insert/delete on views to tables etc, making changes to views seamless. I notice that RazorSQL thankfully still allows me to edit the data in a view if I initiate it by double clicking in the query result, but that the more direct "Edit Table" option in the pop up menu in the entity browser is disabled. Please re-enable it. As for the type of the data to be entered in an update or insert, you can use pragma table_info(tableName) to get the data types of columns in views and tables and implement it to enter the correct data type. Also, RazorSQL should enter null not '' in an insert where data cells are left empty. This is especially a problem for integer primary key columns since '' is not allowed but null is happily accepted and auto replaced by the next integer, but also unnecessarily populates '' in cells where I did not ask for anything to be entered. The incomplete support for editing views is a show stopper problem. Some more points: 7. RazorSQL shows the results of a query in a pane in the main window. When I initiate editing of data there (such as by double clicking on a data cell), RazorSQL opens a new window with a copy of that same table, and I have to locate the data cell again. It would be more intuitive, efficient and streamlined to perform the editing directly in the query result pane, rather than opening a new window. 8. Each query result shows in a new tab in the bottom right panel. They are labeled "Query 1", "Query 2" etc, which gives no indication of their origin. It would be helpful to show the table/view name. 9. The syntax coloring looks great. It would be helpful to have literals (in single quotes) show as a different color to identifiers (in double quotes). It would be even more helpful to show all identifiers (in double quotes or square brackets or unbracketed table/view/trigger/index/column names) in the same color. 10. How about a view of one record at a time, similar to "line" mode, eg: fieldname1: value of fieldname1 in record n fieldname2: value of fieldname2 in record n fieldname3: value of fieldname3 in record n fieldname4: value of fieldname5 in record n This devotes one window/screen to one record at a time, with more room to edit. 11. The SQL formatter (indenting SQL statements) is good idea, but the current implementation is of limited use, since, for instance, it treats commas in the select statement to same as commas within brackets. 12. I struggle with the Java app GUI. Native Cocoa would look and work much better. I'll review more if point 5 (editing of views) is addressed, since then I can find some use for it. Thanks. (Version 4.2.1) | 
