aboutsummaryrefslogtreecommitdiffstats
path: root/Source/SPDataStorage.m
Commit message (Collapse)AuthorAgeFilesLines
* Minimal refactoringMax2015-03-091-3/+3
| | | | Replaced some (range.location + range.length) with NSMaxRange(range)
* Formalize [x release], x = nil; conventionMax2015-01-041-4/+4
| | | | | Take this commit as a proposal to formalize our existing "[x release], x = nil;" convention by introducing a macro for it. Feel free to revert this commit if you see issues with the approch or implementation.
* Reformatting code for modern ObjCMax2014-12-131-1/+1
| | | | | Replaced all [NSNumber numberWithBool:YES/NO] with the @YES/@NO literals. Also replaced some TRUE/FALSE with their YES/NO counterparts.
* Fix a loss-of-precision implicit conversion warningrowanbeentje2014-05-041-1/+1
|
* Improve thread safety of SPDataStorage NSPointerArray tracking to further ↵rowanbeentje2014-02-061-5/+6
| | | | improve #1884 and fix count tracking when removing a single row
* Update NSPointerArray usage in SPDataStorage for 10.9 SDK, tracking edited ↵rowanbeentje2014-02-041-20/+48
| | | | row count and using for fast bounds checks; this should fix #1884
* Update URL in source file header to point to GitHub.Stuart Connolly2014-01-261-1/+1
|
* Remove SVN property placeholder.Stuart Connolly2014-01-261-2/+0
|
* Add an option to display binary data as hex, while displaying it in blue to ↵Stuart Connolly2014-01-141-1/+1
| | | | distinguish from string data of similar content.
* - Fix hanging waiting for new result store to return if there was a query ↵rowanbeentje2013-08-141-1/+1
| | | | error, addressing Issue #1783
* Rework table content and custom query data loading and storage for speed ↵rowanbeentje2013-08-131-232/+246
| | | | | | | | | 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.
* - Fix all the Xcode 4.6.2 build warnings, and tweak warning settings to ↵rowanbeentje2013-05-211-7/+7
| | | | enable some more
* Change Sequel Pro's license from GPL (version 2) to MIT.stuconnolly2012-07-251-13/+20
|
* fixed compiler warningssqlprodev2011-03-011-1/+1
|
* Tidy up.stuconnolly2010-10-191-1/+2
|
* - Improve SPDataStorage exceptions by recording the requested location and ↵rowanbeentje2010-08-011-7/+7
| | | | the storage range
* Tidy up imports and fix 'Reverse Sort Order' when sorting connection ↵stuconnolly2010-03-311-1/+0
| | | | favorites (Thanks Hans).
* - Fix a data storage incorrect reassignment after a realloc - cause of ↵rowanbeentje2010-02-191-5/+4
| | | | source view changes/content view update crashes, and almost certainly memory leaks and other crashes
* - Fix an incorrect bounds check in the data storage class, fixing crashes ↵rowanbeentje2010-01-211-1/+1
| | | | when removing records in a range - seen in Issue #542.
* Add a new SPDataStorage class, and use it in TableContent and CustomQuery:rowanbeentje2010-01-171-0/+424
- SPDataStorage is a class designed for a 2D array of fixed-width data storage, replacing the current method of nested NSMutableArrays. NSFastEnumerator compatible. - Overall memory overhead for table storage in memory reduced by 1.2-1.4x - this almost gains back the large memory jump seen for 64 bit - Some operations (adding data, retrieving a single cell's data) are faster than nested NSMutableArrays; some operations (requesting a row as an NSArray) are slightly slower as the data needs to be converted, but overall result is a slight speed gain. (- Could be used in future to store SQL results in C datatypes, avoiding very high NSObject overhead for numbers and short strings)