| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
- Fix a bug where the socket path would not be autodetected if an empty string was supplied
- Fix a bug fetching primary key column names for tables
- Fix a bug building database structures on MySQL 3.x servers
|
|
|
|
|
|
|
|
| |
- Add a ping keepalive managing object to prevent retain cycles from the NSTimer
- Add -[SPMySQLConnection copy] support
- Refactor Hans-Jörg Bibiko's database structure retrieval, moving it out of the MySQL framework and building it around a copy of the connection. This reduces the amount of connections-over-time used by Sequel Pro to two constant connections (addressing Issue #1097) and improves robustness.
- Use the database structure retrieval connection for faster query cancellation without an extra connection required, if possible
|
|\ |
|
| |
| |
| |
| | |
is being retrieved
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
exceptions as database structure retrieval is currently missing!
Further work on SPMySQLFramework integration:
- Improve SPMySQL framework build settings including correct ppc builds and a Distribution configuration for the build distributions to match
- Add new convenience querying and result methods to the framework
- Amend Sequel Pro source to use the new SPMySQL.framework methods everywhere, replacing MCPKit methods where they differ and improving some functions
- Remove MCPKit from the source
- Fix a number of warnings on Release-style builds
|
| |
|
| |
|
|
|
|
| |
cycles caused by manually loading libs with bindings to File's Owner are automatically handled, fixing leaks of SPConnectionController and items it retain including any MCPConnection; this will fix issues with MCPConnections attempting to reconnect but no longer having an associated SPDatabaseDocument
|
|
|
|
| |
place when checking against the maxium allowed characters. Fixes issue #1237
|
|
|
|
| |
correct server name
|
|
|
|
| |
decide how to deal with NULLs rather than passing them already converted to the user's placeholder prefernce which results in them being quoted. Fixes issue #1281. Also, general tidy up.
|
|
|
|
| |
selecting the default favorite in the general preference pane.
|
|
|
|
|
|
|
| |
- Fix exceptions caused by the sizes column formatter requiring a NSNumber
- When displaying the indexes view ensure the sizes column is hidden by default, as the advanced view is closed - unless a field with a required size has been selected
- If a field with a required size has been selected, don't hide the sizes column when collapsing the advanaced view
|
| |
|
|
|
|
| |
preference.
|
|
|
|
| |
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
|
|
|
|
| |
cause for some unknown reasons an exception
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
|
|
| |
from origin {0,0}; now it's synchronized
• minor speed ups for custom query editor
|
| |
|
| |
|
|
|
|
| |
interface. This addresses Issue #1214.
|
| |
|
|
|
|
|
| |
- Update localizable strings
|
|
|
|
| |
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.
|
|
|
|
| |
message set ensure it's not modified while being enumerated. Fixes exception http://spbug.com/l/2743
|
| |
|
|
|
|
| |
engine/type being quoted.
|
| |
|
|
|
|
| |
time (currently in milliseconds). Implements issue #944
|
|
|
|
| |
informationForTable:] to prevent the inclusion of them in subsequent calls for different tables. Fixes issue 1206.
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
opened not in awakeFromNib. Fixes issue #1198.
|
| |
|
|
|
|
| |
2665
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
.strings files)
|
|
|
|
| |
triggering an export whilst a query is being performed.
|
|
|
|
| |
during CSV import)
|
|
|
|
| |
this addresses Issue #1176
|
|
|
|
|
|
| |
- 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
|
|
|
|
| |
"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.
|
|
|
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
| |
currently used relation names in a backgroud thread. In the event that the user opens the add new relation sheet during this process, the ability to enter a relation name and confirm the addition is disabled until the retrieval process is complete. There is also a new progress indicator on the add sheet to indicate this.
|
| |
|