| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
are mutable
|
|
|
|
|
|
|
| |
mutableCopy when toggling SELECT/SHOWS; it allows the SELECT/SHOWS toggle and text filters to stack together whatever order they are changed in; and it allows both filtering and hiding SELECT/SHOWs to be applied 'live', ie messages added to the console will have the same logic applied to them.
- Clean up trailing whitespace in the file
|
|
|
|
|
|
|
|
| |
(issue #192).
- Also make these messages have a style of critical to indicate the potential loss of data as a result of performing the operation.
- Updated Localizable.strings to accommodate new dialog messages.
|
|
|
|
|
|
| |
- Add the ability to configure the maximum number of items in the query history
- Added appropriate minumums (0) and maximums in prefs for max history items, LIMIT count, connection timeout value
|
|
|
|
|
|
| |
- Add an implementation of NoodleLineNumberView, by Paul Kim. Slightly tweaked to remove markers.
- Add to CMTextView (to enable it for other CMTextView uses, hook up the scrollView outlet to the containing scroll view)
|
|
|
|
|
|
|
| |
preferences and selects appropriately; this resolves the initially planned changes for Issue #232.
- Move updateDefaultFavoritePopup in SPPreferenceController to a public method and set TableDocument to update it when adding favorites
|
|
|
|
|
|
|
|
| |
the + and - buttons, and re-enable double-click to connect. This addresses the majority of Issue #232, although the "Edit" button is not yet functioning.
- Fix a bug where if an autoconnection failed, connection was automatically reattempted
- Add a name field to the connection sheet, and display the name in the window title in place of user@host if set
|
|
|
|
|
|
|
| |
directly to pick up updates more quickly
- Improve favouritesAlreadyExists check to respond correctly if the connection database, host or user is blank
|
|
|
|
| |
back and testing older releases/revisions
|
|
|
|
| |
remove '_dump' and spaces from filename.
|
| |
|
| |
|
|
|
|
| |
value is NULL (fixes Issue #229)
|
|
|
|
| |
versions for testing/usage
|
|
|
|
|
|
|
|
| |
ith the keychain. This resolves the last part of Issue #186 and associated problems (ie multiple connections via a tunnel with only the port differing - now can store different passwords).
- Duplicate function in prefs now also duplicates the password
- Fix a few places which created a blank keychain entry when no password was present
|
|
|
|
|
|
| |
- Add the keyboard shortcuts advertised on the button tooltips to the buttons
- When duplicating a favorite, append " Copy" to the name to ensure the keychain password isn't automatically shared and therefore accidentally changed or deleted for both when one favorite is edited.
|
|
|
|
|
|
|
|
| |
preferences window
- Remove the now unnecessary (and never implemented) "Save" button below the favorites editor
- Hook up the Remove and Duplicate favorite buttons to the correct Enable binding
|
| |
|
|
|
|
| |
avenjamin for the suggestion!)
|
|
|
|
|
|
| |
- Restore pref upgrade methods, make compatibible with both lastUsedVersion and LastUsedVersion keys
- Add upgrade method to map old pref keys to new pref keys, delete old keys
|
|
|
|
| |
complex notification rules.
|
| |
|
|
|
|
|
|
|
| |
- Update a few pref checks which were using the old pref values still
- Resort preference defaults to match layout in prefs, restore old default values for some keys
- Restore missing defaults for new editor properties
|
| |
|
|
|
|
| |
automatic creation methods to only trigger automatic connection (if enabled in prefs) for automatically created windows
|
|
|
|
| |
- Changed "nullValue" to "NullValue"
|
|
|
|
| |
- committing Source
|
|
|
|
| |
current connection details to your favourites provided it doesn't already exist.
|
| |
|
|
|
|
| |
ensure the connection encoding is similarly reset. This addresses Issue #79.
|
|
|
|
| |
renaming a favourite wouldn't update the associated Keychain item. The item is now updated whenever the favourite name is changed.
|
|
|
|
| |
decimal places instead of one)
|
|
|
|
| |
them in sheets instead of modal dialogs. Also performed a general tidy up of TableDocument.[hm].
|
| |
|
|
|
|
| |
• some minor code cosmetics
|
|
|
|
| |
queries are sent as UTF8, if possible; this correctly preserves encoding data when working with files export from Sequel Pro or via mysqldump, and attempts to fall back to the current connection encodings for other files. This should resolve Issue #116.
|
|
|
|
| |
• keyword update for completion
|
|
|
|
| |
• ADDED: if caret is inside quotes "" or '' show Apple's default completion list due to the spell checker settings
|
|
|
|
| |
• syntax highlighting updated
|
|
|
|
| |
auto-uppercasing
|
|
|
|
|
|
| |
be a SQL keyword
- e.g. type inta and then press deleteBackward:
|
|
|
|
|
|
| |
of the textStorage
- this fixes also auto-uppercasing for runAll/Current/SelectionQueries
|
|
|
|
| |
- added highlighting for @vars
|
|
|
|
|
|
| |
• added syntax highlighting for numeric values
• changed syntax highlighting for 'order' and 'group' to 'order by' resp. 'group by' (useful also for visual syntax checking while typing)
• fixed the issue to highlight a keyword if that keyword is the name a variable (e.g. @set := 1)
|
|
|
|
| |
textStorageDidProcessEditing: to avoid the deletion of a given selection
|
|
|
|
| |
count.
|
|
|
|
|
|
|
| |
and before performQueries
• improved undo behaviour of auto-uppercasing
• added undo behaviour for pasting queries from favourites & history
|
| |
|
|
|
|
|
|
|
| |
backup-type process and more closely match mysqldump, and correctly drop views
- Consistently set and restore the encoding appropriately for SQL import/export, and export to UTF8 files to correctly store all characters. Goes a good way towards addressing Issue #116.
|
|
|
|
|
|
|
| |
would be greater than the total number of rows of the current table
• FIXED: if the user enters into "Limit from" a number which is greater than the total number of rows of the current table, show the last pref's "limitRowsValue" number of rows instead
• FIXED: if the user has already filtered the current table by specifying "Limit from" > 1 and afterwards the user applied a new filter the filtering will be repeated for LIMIT 0, "limitRowsValue" if nothing was found
|