| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
- SP tried to select the erroneous part in customQueryView which could lead to an range exception
- now it shows a proper error message
- it suppresses column highlighting and setting of the NSSortIndicator
|
| |
|
|
|
|
|
|
|
|
|
| |
- ⌘/ (un)comment current line only if no selection is given (by using "-- ")
-- caret jumps to the next line to (un)comment lines quickly
-- # sign will be recognized for uncommenting as well as if the entire line is wrapped into /* */
- ⌘/ (un)comment current selection (by wrapping it into /* */)
-- it (un)escapes present */ into *\/ automatically
- ⌥⌘/ (un)comment the current query (by wrapping it into /* */)
-- the GUI element will be found in the Gear Menu by pressing ⌥
• added shortcut ⌫ to Table Content's "Delete selected row(s)" tooltip
|
| |
|
|
|
|
|
| |
- changed comment string to "-- "
- fixed bug in uncomment
- added gear menu item
-- TODO: change menu item title according to selection/current query (coming soon)
|
| |
|
|
|
|
| |
current query or selection by inserting "# " at the begin of each line
- Note: not yet finished completely
|
| |
|
|
|
|
|
|
|
|
|
|
| |
arrays, and make some editable CustomQuery improvements:
- Switch to using arrays for row storage rather than dictionaries. Use the data column index for table column identifiers.
- This fixes Issue #316 and also allows sorting by all custom query result columns using a column index rather than the name
- Offers significant speed and memory advantages: result building is now 2x-3x faster, memory used for results storage is 30-40% lower, and result access is slightly faster. (Note full 2x-3x speed results won't be seen - result fetching and mysql binary work isn't included in the timing)
- No longer need to fetch the first column of data for tables containing only blob types
- Correctly escape strings when editing CustomQuery results
- Rewrite NSArrayObjectAtIndex to use the native CFArrayGetValueAtIndex rather than cached selectors - neater code and I think slightly faster
|
| |
|
|
| |
at a column header
|
| |
|
|
|
| |
- preserve table width/order after editing
- updated data source code to avoid having the data twice in the memory
|
| | |
|
| |
|
|
|
|
| |
containing a `
• some minor code cleaning and commenting
|
| |
|
|
| |
such fields which can be identified bijectively by the given table data
|
| |
|
|
|
|
| |
- CustomQuery table now allows to copy selected rows as SQL INSERT (table name is set to "<table>"
- if a field is a blob display only the first 255 bytes/chars in the CQ table for speed reasons
- blob fields in CQ does not listen to the pref setting for "LoadBlobsAsNeeded" because it could happen that no one-to-one relation to their original data will be found
|
| |
|
|
|
| |
- "Query Background" color
- checkbox "Highlight Current Query"
|
| |
|
|
| |
• added: "Select Active Query ^Y" context menu item to the Custom Query Editor
|
| |
|
|
|
|
| |
• added queryRangeAtPosition: method because this is needed also for other purposes
• moved the commands for highlighting the current query from queryAtPosition: to textViewDidChangedSelection: (where it belongs to)
• some minor changes in error highlighting code
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- added
(NSArray *) splitSqlStringByCharacter:(unichar)character;
(NSArray *) splitSqlStringIntoRangesByCharacter:(unichar)character;
(long) firstOccurrenceInSqlOfCharacter:
to the SQLParser which recognize a “delimiter” command
• queryAtPosition now works with ranges to speed it up
- the current query ranges resp. the just activated query range are cached in order to avoid parsing if the user only navigates through the textView buffer, or if the user calls Run Prev/Current Query only
• the "import dump" function makes usage of that new “delimiter” support
- i.e. dumps with procs/funcs declaration could be imported
IMPORTANT: Please check the new SQLParser exhaustively in order to prove that new approach
|
| | |
|
| |
|
|
|
|
| |
- it shows the MySQL Help TOC of the front most tableDocument mysql connection, i.e. each tableDocument has its own Help window (due to the fact that the Help is version specific), and makes it the keyWindow
- changed the way for getting the mySQLversion into the CustomQuery; now a new tableDocument set it via [customQueryInstance setMySQLversion:foo]; the other way was to unsafe regarding to get the version if MySQL Help was invoked via MainMenu
• Help window and Create Table Syntax window will be released while closing the tableDocument
|
| |
|
|
|
| |
• prepared code to work with autoHelp
• improved getRangeForCurrentWord (fix for " |a")
|
| |
|
|
|
|
| |
- updated autoHelp, now it recognizes cursor movement via mouse
• if the chunk in CQ's textview is too large remove all attributes
• some minor code cosmetics
|
| |
|
|
|
| |
- refactored and cleaned contextMenuItems for the webview
- help-html-template will be loaded only once
|
| | |
|
| |
|
|
|
| |
- change help target buttons into a NSSegmentedControl
- fixed minor typo
|
| |
|
|
|
|
|
| |
- added history: go back/forward
- window now has auto save name MYSQL_HELP_WINDOW
- disabled contextual menu for safety reasons (temporarily)
- some minor stuff
|
| |
|
|
|
|
|
|
|
| |
- added help target (online, in current page, in MySQL help ⌥⌘O,P,M)
- GUI support for go back/forward (not yet implemented)
- ⌘G, ⇧⌘G for find next/prev in current page
- ⌘F selects search field; ⌘+ and ⌘- support
- online search is version sensitive
|
| |
|
|
|
|
| |
- better HTML view, list topics for multi-matching keywords
- for test cases invoke it by CTRL+H in the Custom Query textView
- GUI is really tentative!
|
| |
|
|
|
|
| |
Custom Query text view
- work in progress!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
asked to "Stop", "Continue" or "Run All"
- Stop: the execution will stop at the erroneous query (if other queries would follow "Execution stopped!" will be prompted in the error message field)
- Continue: continues the execution but shows that alert for a next error
- Run All: runs all following queries regardless of possible errors
• improved the error selection
- fixed the issue for Run Current/Previous (even for duplicates)
- if no error line is given it selects the first query which caused an error entirely
- due to the localization of mysql error messages changed the regexps for catching the:
-- line number to /([0-9]+)$/ because the line number always should be outputted at the end
-- "near message" to / '(.*?)' / (important the last space because after that space the line number will be outputted)
-- further checks are needed
|
| |
|
|
| |
behaviour for the "Run current"/"Run selection" button is triggered if the text caret is only separated by whitespace from the last query, to allow easy running of a just-typed query
|
| |
|
|
|
|
|
|
|
| |
• added error highlighting of the first mentioned error
- if a "near message" error is provided select that message otherwise select the entire error line and scrolls to it
- if no "at line x" and no "near message" is given do nothing
- if a selection was given and the user pressed "runAll" destroy the selection before error checking; if no error was found reconstruct that selection (to be able to distinguish between "runSelection" and "runAll" plus selection)
* changed slightly the trigger for syntax highlighting/auto-uppercasing for better scrollToRange behaviour
|
| | |
|
| |
|
|
|
|
|
|
| |
invalid log entries
- Set the focus to the custom query text field when appropriate when switching to the custom query tab
- Add the ability to set the custom query editor font, save and load it from preferences, and no longer reset the font on queries
|
| |
|
|
| |
in the text view, currently off by default but saved from preferences. Thanks again to Hans-Jörg Bibiko for this patch; see Issue #218.
|
| |
|
|
| |
- Changed UI in Query Tab for favourite and history popups as well as Run query buttons
|
| |
|
|
|
|
|
|
|
|
|
|
| |
a number of items:
- Add menu commands for "Run All" and "Run Selected", with additional keyboard shortcuts - cmd-R for Run all, addressing #137
- Add menu commands for indenting text, outdenting text, and to show autocompletion is available
- Add menu commands to toggle autopairing and autoindenting
- Also hidden menu commands for history navigation and clearing, not hooked in yet (see #207)
- Add a new method to our string additions: lineRangesForRange
- Add "shift right" (indent) and "shift left" (outdent) support to CMTextView, including for multiple lines
|
| |
|
|
|
|
|
|
| |
for the original patch (see http://code.google.com/p/sequel-pro/issues/detail?id=208 for full details). Applied with slight amendments.
- Further changes to make CMTextView more standalone and reusable - autopairing and autoindenting can now be enabled/disabled and checked.
- Autopairing and autoindenting moved to app preferences.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Use method caches for oft-called functions, and support caching of chunks of the underlying string for string walking, resulting in an overall 1.3x-1.4x parsing speedup.
- Improve handling of multi-character comment starts (eg / or -) at the very end of strings
- When running splitString... methods return even empty strings for consistency.
- Update TableDump and TableData to match new usage
SPStringAddition changes:
- Add a formatter for time intervals.
CMMCPConnection changes:
- Add support for timing queries
CustomQuery and nib changes:
- Change the "Run Queries" button to "Run All".
- Add a "Run Current" button, which runs the query the text caret is currently positioned inside; if text is actually selected, this changes to "Run Selection". This addresses Issue #43.
- Amend the "rows affected" string to better reflect the actual number of rows altered by several queries, show the query count if > 1, and display the overall execution time of the queries. This addresses Issue #142.
- No longer execute blank strings as part of the custom query, preventing errors.
|
| |
|
|
|
|
|
| |
plus/minus buttons. Also add some interface element validation.
- Tidy up CustomQuery.h by getting rid of the definition of all datasource and delegate method signatures which don't need to be declared.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Significantly reduce the queries that have to be performed, improving lag - especially over slow connections (Issue #118; see new controller info under headline code changes).
- Fix Issue #117 properly (export numeric quoting - we now have access to column types and so can quote appropriately).
- Fix Issue #145 (loss of unsigned/null/default attributes when reordering columns).
- Fixes Issue #90 (support for filtering DECIMAL column types)
- Improve table scrolling speed when the table contains long items. (Added a NSFormatter to automatically truncate strings > 150 chars for display purposes only)
- Improved SQL compatibility - for example /* C style comments */ are now correctly ignored in imports and custom queries.
- Add text and symbols emphasising that the table info pane / status view row count is an approximation (partially addresses Issue #141)
- Fixes a major memory leak whenever opening or scrolling tables containing text/blob data.
- SQL import is now faster (SQL parsing part is 3x faster).
- Speed up SQL export (1.5x faster for numeric data; 1.1x faster for string data) and slightly speed up CSV export (~1.1x faster).
- Display sizes on the status view using the byte size formatter, as per table info pane.
Headline code changes:
- Add a new NSMutableString subclass, SPSQLParser. See the header file for documentation and overview, but in short it's a centralised place for SQL parsing. Centralises and improves parsing, improves comment support, improves quoting support. Despite the improved featureset this is also faster than the previous distributed implementations - for example, when used to replace the old splitQueries:, > 3x speedup.
- Implement a new controller which handles a structure and status cache for the current table, and provides structure parsing for specified tables. This cache is now used throughout the code, reducing the queries that have to be performed and providing additional information about the table structure for use; I think it also improves column type format slightly.
- The table info pane and the status view now draw all their data from the cache.
Tweaks:
- Table encoding is now detected directly instead of being derived from the collation - increased accuracy and cope with the DEFAULT encoding.
- Comments and formatting cleaned up in bits I was working on, obviously.
- A couple of methods - particularly [tablesListInstance table] and [tableDocument encoding] - have been renamed to avoid conflicts and fix code warnings.
Future improvements now possible:
- As we now have access to column types and other information, we can provide per-type behaviour where desired.
- The table parsing doesn't currently pull out comments or table indices, together with one or two other attributes. Some of this would be useful for display; some, such as indices, could be used to draw the table structure view as long as we're happy discarding a couple of columns (ie cardinality!)
|
|
|
structure.
|
