aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* - Roll back r3453 to avoid future license issuesrowanbeentje2012-01-101-3/+3
|
* Fix the indexes view not restoring the use vertical table view gridlines ↵stuconnolly2012-01-091-0/+1
| | | | preference.
* - Expicitly cast parameters before passing into NSString formatters ↵rowanbeentje2012-01-095-7/+7
| | | | assuming 64-bit lengths; this addresses exceptions and hangs viewing table contents on 32-bit machines, many thanks to stuart02 for identifying and tracking down this issue
* • removed for syntax hiliting "ensureLayoutForCharacterRange" since it can ↵Bibiko2012-01-081-4/+0
| | | | cause for some unknown reasons an exception
* - Add a new CSV import field escape setting, as a new default, supporting ↵rowanbeentje2012-01-065-3466/+3508
| | | | both backslash and double-character escaping. This will mean the vast majroty of CSVs selected for import will be read correctly by default, fixing issues such as Issue #1252
* • removed setting of textColor after syntax hilitingBibiko2012-01-051-11/+0
|
* • removed blocking of SPTextView textStorage while syntax hiliting Bibiko2012-01-051-2/+2
|
* • fixed issue for line numbering view if associated textView is scrolled ↵Bibiko2012-01-054-32/+63
| | | | | | from origin {0,0}; now it's synchronized • minor speed ups for custom query editor
* • sped up the line number drawing; now it's 5 times fasterBibiko2012-01-052-20/+30
|
* - Add Zend Server CE compatibility to the default socket search list, path ↵rowanbeentje2012-01-051-0/+1
| | | | as given in Issue #1251
* - Fix compilation errors reported by pornelski in Issue #1253rowanbeentje2012-01-041-3/+3
|
* Update Growl framework to version 1.2.3 to fix compatibility with Growl 1.3. ↵stuconnolly2011-11-054-5/+21
| | | | Fixes issue #1220.
* - Fix an issue in MCPConnection causing connection locking if the ↵rowanbeentje2011-10-281-1/+17
| | | | connection has an active query and is performing actions such as encoding conversions
* - Fix addition of new passwords for favourites edited via the Preferences ↵rowanbeentje2011-10-201-4/+14
| | | | interface. This addresses Issue #1214.
* - Fix two incorrect initialisations; thanks to sqlprodev for spotting theserowanbeentje2011-10-202-2/+2
|
* - Update code to use NSStrings for NSTableColumn identifiers, as per 10.7 SDKrowanbeentje2011-10-178-90/+63
| | | | | - Update localizable strings
* - Improve the favourites editing process to edit keychain items, rather ↵rowanbeentje2011-10-163-22/+84
| | | | than deleting and recreating them. This has two advantages: firstly, it matches the Apple recommendation, as it preserves keychain item access lists and comments for keychain items when they are edited; secondly, it works around a bug in 10.7 which appears to be a Keychain cacheing issue, causing password retrievals to return the original keychain item on launch - which is no longer valid after deletion/recreation. This addresses Issue #1197.
* When building a string of all console messages, use a copy of the visible ↵stuconnolly2011-10-161-2/+8
| | | | message set ensure it's not modified while being enumerated. Fixes exception http://spbug.com/l/2743
* Update donate URL.stuconnolly2011-10-091-1/+1
|
* For some reason table creation on MySQL 4.0 servers doesn't like the ↵stuconnolly2011-10-094-33/+44
| | | | engine/type being quoted.
* * Move key of a hidden pref to the same place as the othersdmoagx2011-10-092-2/+2
|
* Add a hidden preference for specifying the long running query notification ↵stuconnolly2011-10-085-8/+12
| | | | time (currently in milliseconds). Implements issue #944
* Layout fixes.stuconnolly2011-10-081-16/+18
|
* Ensure the that table constraints are cleared in [SPTableData ↵stuconnolly2011-10-082-33/+34
| | | | informationForTable:] to prevent the inclusion of them in subsequent calls for different tables. Fixes issue 1206.
* * Fixes a minor bug where the server time zone would not be detected correctlydmoagx2011-10-071-1/+2
|
* - Rework table data saving to ensure that cells that should be edited via ↵rowanbeentje2011-10-056-324/+307
| | | | | | | the edit sheet aren't then overwritten by the cell value, potentially causing data truncation in 10.5. This addresses Issue 1196. - Consolidate field editing in sheet logic
* - Update database encoding routines to cache the database encoding, ↵rowanbeentje2011-09-292-6/+25
| | | | | | | preventing repeated calls when navigating tables using "default" encoding, or views - Ensure the database encoding is correctly updated when new databases are selected. This addresses Issue #1201
* Set the previously used export filename and path when the export dialog is ↵stuconnolly2011-09-291-23/+43
| | | | opened not in awakeFromNib. Fixes issue #1198.
* Fix IB warnings.stuconnolly2011-09-271-97/+115
|
* Fix IB warnings.stuconnolly2011-09-271-8620/+8648
|
* QueryKit updates.stuconnolly2011-09-273-5/+8
|
* Fix test.stuconnolly2011-09-265-17/+26
|
* * Add French translators to credits (translation mostly done, so we can ↵dmoagx2011-09-241-12/+36
| | | | include it in next release)
* - Fix editing of binary string values, a regression in r3428; addresses log ↵rowanbeentje2011-09-222-0/+6
| | | | 2665
* Rework linebreak handling in content and custom query result views, as ↵rowanbeentje2011-09-215-37/+141
| | | | | | | | | | | triggered by Issue #1184: - Display table cells on a single line for preview purposes - Display gray pilcrow/reverse pilcrow placeholders instead of linebreaks - If a cell contains linebreaks, automatically trigger sheet editing mode - Handle newly displayed linebreaks in column width detection - If using the up/down arrow keys in a field editor, allow them to select the previous/next line within an editor if appropriat (instead of always moving to the previous/next row)
* Fix test suite crashing.stuconnolly2011-09-181-8/+1
|
* * Add "Copy CREATE *" to context and gear menu, fixes #1190 (updated ↵dmoagx2011-09-157-63/+170
| | | | .strings files)
* Improve custom query result export menu item validation to prevent ↵stuconnolly2011-09-131-1/+1
| | | | triggering an export whilst a query is being performed.
* - Improve time zone checking to account for NULL timezones, which should ↵rowanbeentje2011-09-121-3/+3
| | | | address Issue #1181
* QueryKit comments.stuconnolly2011-09-122-4/+13
|
* - Speculative fix for Issue #1154 (problems using some field separators ↵rowanbeentje2011-09-121-0/+3
| | | | during CSV import)
* QueryKit additions.stuconnolly2011-09-107-26/+292
|
* Update QueryKit license to be MIT.stuconnolly2011-09-109-100/+163
|
* - Add the ability to view hidden files in SSH/SSL key selection dialogs; ↵rowanbeentje2011-09-108-24441/+25239
| | | | this addresses Issue #1176
* - Make add relation error detail intro localisablerowanbeentje2011-09-093-1/+7
| | | | | | - If the add relation error strongly appears to be a name-already-taken error, add the name to the takenNames list to prevent it being used again and to highlight the error - Update localisable strings
* - Update FeedbackReporter framework to no longer capture the console log on ↵rowanbeentje2011-09-081-0/+0
| | | | 10.5.8/PPC machines. This gives us slightly less diagnostic ability, but prevents crash loops for feedback/exception/crashes, addressing Issue #1175
* - Require there to be at least 50 rows to be in the table before using the ↵rowanbeentje2011-09-071-1/+1
| | | | "DELETE FROM foo" remove all rows code path. This improves the chance that the user actually intends to delete all the rows in the table, addressing Issue #1166.
* Rework relation addition and name lookups following testing and research:rowanbeentje2011-09-073-96/+56
| | | | | | | | - Remove the background lookup of table constraint names for the current database. This prevented connection use while the query was running, and the query cannot be optimised and severely taxes servers with many databases. Revert to checking names against names in the current database - Repurpose the activity spinner for adding relation query execution - When an error is encountered adding a relation, re-open the sheet with the submitted values after displaying the error - Add use of 'SHOW InnoDB STATUS' command and text extraction to show more explicit errors for the most common constraint errors
* More QueryKit progress. Still very rough.stuconnolly2011-09-065-17/+107
|
* Add the beginnings of QueryKit.stuconnolly2011-09-0414-8/+922
|