aboutsummaryrefslogtreecommitdiffstats
path: root/Source
Commit message (Collapse)AuthorAgeFilesLines
* Fix issue with app beachballing when connecting from external URL (#2903)Max2018-04-203-2/+29
| | | | Let’s hope this won’t break on older OS versions now…
* Replace a macro with a block (C > preprocessor) and reformat some codeMax Lohrmann2018-04-171-89/+101
|
* Fix crash when trying to print on 10.13.4 (#3025)Max2018-04-133-12/+24
|
* Source formatting changesMax2018-04-121-193/+190
|
* Names of newly created favorites could be overwritten with the host name ↵Max Lohrmann2018-04-031-60/+23
| | | | | | under specific conditions (#3015) Also minified some duplicate code along the way
* Parser support for NO_BACKSLASH_ESCAPES (part of #3005)Max Lohrmann2018-03-212-85/+120
|
* Reapply changes from rolled back commit that are common to master and ↵Max2018-02-285-66/+51
| | | | | | callback-auth branches This includes 3a944d7867c750c29e02e2619d72694bdbfb0b2a, 770c18901f82696d1233e0139e9bb3c4fbbcb90b, ca864a1f887feaf7ac6d35eeb55b265f3e630a09
* Manually roll back all changes for #2979Max2018-02-276-217/+87
| | | | Those will be moved to a different branch for the time being since other stuff needs to be changed first
* #2979, #2437, #2247, #1836: Enable mysql cleartext auth without access to ↵Max2018-02-244-18/+166
| | | | keychain and with a warning to the user
* #2979: Rename a method, because it is no longer limited to keychainMax2018-02-232-5/+5
|
* Remove the keychain id stuff from SPDatabaseDocument. It was only proxying ↵Max2018-02-234-35/+27
| | | | SPConnectionController anyway
* Move method -keychainPassword from SPDatabaseDocument to ↵Max2018-02-233-20/+17
| | | | SPConnectionController since all it did was request info from the connection controller
* Replace getter/setter glue with propertyMax2018-02-232-23/+8
|
* Next step in the #2979 experimentMax2018-02-182-10/+18
|
* previous commit continuedMax2018-01-203-20/+22
|
* Work around some cases of „background thread manipulating ui“ during CSV ↵Max2018-01-202-77/+107
| | | | import (as reported by Xcode)
* Merge remote-tracking branch 'origin/mergeclasses'Max2018-01-20135-12878/+9896
|\ | | | | | | | | | | | | Conflicts: Source/SPQueryControllerInitializer.m Source/SPQueryDocumentsController.m Source/SPQueryFavoriteManager.m
| * merge and restructure remaining smaller stuff in main project (part of #2789)Max2018-01-2025-240/+134
| |
| * merge SPExportController (part of #2789)Max2018-01-2033-3881/+2822
| |
| * merge SPUserManager (part of #2789)Max2018-01-205-456/+307
| |
| * merge SPQueryController (part of #2789)Max2018-01-2015-811/+595
| |
| * merge some smaller classes (part of #2789)Max2018-01-2013-271/+124
| |
| * merge SPTableStructure (part of #2789)Max2018-01-208-1328/+1151
| |
| * merge SPTableContent (part of #2789)Max2018-01-2011-1467/+1213
| |
| * merge SPConnectionController (part of #2789)Max2018-01-2013-2040/+1649
| |
| * Merge SPDatabaseDocument (part of #2789)Max2018-01-2027-1487/+1235
| |
| * Merge SPWindowController (part of #2789)Max2018-01-203-497/+412
| |
| * Merge SPAppController (part of #2789)Max2018-01-2013-414/+261
| |
* | Remove another 2 cases of very strange object notification behavior (code style)Max2018-01-178-20/+28
| |
* | Work around an exception that would occur when changing Query Favorites ↵Max2018-01-176-45/+37
| | | | | | | | while an unconnected connection tab existed (#2266)
* | Restore a tiny bit of the indentation Xcode just hosedMax2018-01-131-53/+61
| |
* | Replace all calls to deprecated method ↵Max2018-01-137-115/+95
| | | | | | | | +propertyListFromData:mutabilityOption:format:errorDescription:
* | Replace all calls to deprecated method ↵Max2018-01-1311-902/+1005
| | | | | | | | +propertyListFromData:mutabilityOption:format:errorDescription:
* | Change the way SPTextView loads theme colors to prevent loading invalid ↵Max2018-01-132-31/+72
| | | | | | | | colors (which could have been stored in prefs before the previous commit) (part of #2963)
* | Rewrote the theme loading method because it would too easily accept invalid ↵Max2018-01-131-72/+103
| | | | | | | | data (part of #2963)
* | Fix an issue where the contents of a duplicated query favorite would be ↵Max2018-01-051-4/+12
|/ | | | overwritten if the selection was changed bevore saving (#2938)
* * Moved `-[SPHistoryController currentlySelectedView]` to SPDatabaseDocument ↵Max2017-12-0210-89/+109
| | | | | | | (was completely out of place there) * Removed some redundant code in the process * Remove a few cross-thread UI calls Xcode 9.2 complains about (but there are just so many...)
* SQL export used the wrong syntax for view placeholders when the columns ↵Max2017-11-171-1/+6
| | | | contained a type with decimals (#2927)
* Fix a rare timing-sensitive crash when closing a window during a connection ↵Max2017-11-171-1/+4
| | | | attempt (part of #2924)
* Fix a case of "background thread updating UI" (#2916)Max Lohrmann2017-11-112-1/+3
|
* For UTF16 and UTF32 encoded files the charset autodetection logic did not ↵Max2017-09-061-1/+25
| | | | return a specific enough value, resulting in Cocoa sometimes guessing the wrong byte order even when a BOM was present (part of #2860)
* MariaDB 10: SP used a case sensitive check for „CURRENT_TIMESTAMP“ which ↵Max2017-09-031-2/+2
| | | | failed on recent MariaDB versions due to changes to the „SHOW CREATE TABLE“ output (#2876)
* #2863 fix LHS table views when dragging a tab off a windowAbhi Beckert2017-08-252-0/+13
|
* Add a 24-hour-format export filename token.Michael Rog2017-08-074-18/+25
|
* MariaDB 10.2.1+: Work around an exception when trying to view tables that ↵Max2017-06-181-98/+107
| | | | use row-level CHECK constraints
* Fix an error where Sequel Pro would crash when loading the list of Stored ↵Max Lohrmann2017-06-101-1/+2
| | | | Procs/Funcs (probably related to MySQL 5.8/8.0)
* Fix an issue that could cause Sequel Pro to become unusable when reloading a ↵Max2017-06-071-11/+12
| | | | table when at the same time editing a cell with a value that is not valid (#2816)
* Change the way index deletion works (part of #2811)Max2017-06-061-60/+104
| | | | | | * Instead of trying to figure out if an index is used by an FK ahead of time Sequel Pro will now simply run the query and check for the error code (and only for error 1553 will it attempt to also remove the FK) * This means that a user will receive two remove dialogs in this rare case, but I think that is actually preferable. Common wisdom shows that users never read the first warning dialog, so in the past they may have agreed to something that they didn’t intend to do. The second dialog should actually make them pause and read it. Also there is a different confirmation button now. * This also fixes the code to detect which FK in particular MySQL is referring to. SP should now correctly handle compound indexes and multi-column FKs as well as ambiguous results.
* Now that was some silly code… (part of #2811)Max2017-06-051-1/+4
|
* Small changes to PR #2807 and surrounding codeMax Lohrmann2017-05-305-17/+35
|