| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
* [NSDictionary dictionary] → @{}
* [NSDictionary dictionaryWithObject:forKey:] can safely be replaced. object==nil would have already thrown a NPE in the past.
* Also replaced some (hopefully safe) NSArray initializers (ie. their objects should always exist).
|
|
|
|
|
| |
* (Also changed some outdated URLs)
* Replaced [NSApplication sharedApplication] with NSApp
|
|
|
|
|
| |
Replaced all [NSNumber numberWithBool:YES/NO] with the @YES/@NO literals.
Also replaced some TRUE/FALSE with their YES/NO counterparts.
|
| |
|
|
|
|
| |
recommend settngs removing this
|
|
|
|
| |
arguments
|
| |
|
|
|
|
| |
This commit adds the backend code to get the mysql SQLSTATE error code (to be used when displaying errors).
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
sub-projects
|
|
|
|
|
|
|
|
| |
This is documented as being the default, but setting this has resulted in a smaller binary and lower CPU usage with compressed MySQL connection transport.
- Rebuild the libraries with the new setting
- Update localisable strings
|
|
|
|
|
| |
- Tweak the build script to clarify it is now only building a two-way binary and to explicitly not build the server using the new syntax
|
|
|
|
| |
queries which don't produce a result set following the data store changes
|
| |
|
|
|
|
|
|
|
|
|
| |
increases and lower memory usage:
- Add a new SPMySQLStreamingResultStore class to SPMySQL.framework. This class acts as both a result set and a data store for the accompanying data, storing the row information in a custom format in a custom malloc zone.
- Amend SPDataStorage to wrap the new class, so original result information is stored in the one location in the custom format. Any edited information is handled by SPDataStorage for clean separation
- Rework table content and custom query data data stores to use the new class. This significantly speeds up data loading, resulting in faster data loads if they weren't previously network constrained, or lower CPU usage otherwise. The memory usage is also lowered, with the memory overhead for many small cells being enormously reduced.
|
| |
|
|
|
|
| |
enable some more
|
|
|
|
| |
Issue #1708
|
|
|
|
| |
SPMySQLEmptyResult expects a SPMySQLStreamingResult/SPMySQLFastStreamingResult (Exception #3988)
|
|
|
|
| |
instead of nil if a query produces no result set. This allows per-result-set properties to be preserved, fixing issues where information like query execution time was lost - addressing Issue #1577
|
| |
|
|
|
|
|
|
|
|
|
| |
- Update base SDK to 10.6
- Update minimum OS version to 10.6
- Update all XIB to have a 10.6 target
- Drop support for PPC
- Apply all of the above to frameworks SPMySQLFramework and QueryKit
|
| |
|
|
|
|
|
|
|
| |
result of r3894, attempting to improve some exceptions during aborted connections
- Name threads created in SPMySQL.framework
|
|
|
|
|
|
|
|
|
| |
disconnections from external actions, and use that separation to perform safer disconnects
- When closing a database document, add a new notification, and use that to resolve retain cycles affecting connection processes
- Improve connection controller disconnection when the document is closed, fixing crashes, by building on those two features (addresses Issue #1396)
- Use some of the new functionality to improve SSH and MySQL connection cancellation, making both cancelable in the interface and making both respond much more quickly
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
4.5, keeping a base SDK of 10.5 for compatibility for otherwise adding and adjusting settings appropriately
- Add instructions to the README for Xcode 4 SDK installation.
|
| |
|
|
|
|
|
|
| |
Updated QueryKit project to be able to build and run tests (changed Symbols Hidden By Default to NO in Default config)
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
address Issue #877:
- On servers with very short timeouts set the wait_timeout for the session as well as the interactive_timeout to prevent the connection from dropping frequently
- Improve recovery from connection errors, correctly restoring the connection if appropriate and possible
- Allow reconnections to occur recursively by altering the internal tracking mechanism
- Fix some edge cases where the connection would remain locked incorrectly
- Improve error messaging for the "MySQL Server has gone away" network case
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
reviewing crash logs and testing a number of situations:
- Improve stability of closing connections after a connection loss
- Minimise prompting a user for connection state restore if closing windows/tabs
- Allow cancellation of keepalive ping threads to prevent crashes after deallocation of parent
- Manually handle ping thread state struct memory to avoid cross-thread deallocation issues
- Improve disconnection speed and resilience
|
|
|
|
| |
of a reference to the retained error string to avoid any overrelease errors later affecting the framework
|
|
|
|
| |
paths, improving general connection robustness in recent builds
|
|
|
|
|
| |
- Improve debug to catch a structure connection issue
|
|
|
|
|
|
|
|
|
|
|
|
| |
background loss of connections:
- Attempt to fix a condition causing a reconnection loop by fixing the order of connection state check and a query variable
- If a connection is lost in the background, only attempt a single reconnect instead of requiring user intervention at once
- Add a new connection state to handle background disconnects
- If the connection has been lost in the background but is about to be used, reconnect it automatically (informing the user of loss if appropriate)
- Don't attempt background reconnections if the connection has not been used for some time
(Also update localisable strings, and tweak navigator controller connection usage)
|