| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
displaying table contents, as it saves a lot of shouldUseFieldEditorForRow: checks; shortStringRepresentationUsingEncoding: should return the same values for short strings
|
|
|
|
| |
for use when loading tables, which may improve Issue #1925 and Issue #1902.
|
| |
|
| |
|
|
|
|
| |
distinguish from string data of similar content.
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
in-place, addressing Issue #1702
- Ensure that truncation of data values includes an ellipsis to make it clear when performance-based truncation is occurring
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
fix nightly builds
- Fix warnings
|
|
including the entire content of BLOBs, not just what we display. Fixes issue #1124.
- Move SPTableContent's table view datasource and delegate methods to separate categories in order to reduce it's size.
|