| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
menu item View > Table Triggers (apple-6).
Heavily copied from Relations tab, lots of functionality missing. Just
lists the triggers for the table now.
M Source/SPTableData.m
M Source/SPConstants.h
M Source/SPConstants.m
A Source/SPTableTriggers.h
A Source/SPTableTriggers.m
M Source/TableDocument.h
M Source/TableDocument.m
M Source/SPTableData.h
M Interfaces/English.lproj/MainMenu.xib
M Interfaces/English.lproj/DBView.xib
M sequel-pro.xcodeproj/project.pbxproj
|
|
|
|
|
|
|
|
| |
textviews
• added Preference setting "Table font" in "Table" pane to set the table font/size for all result tables (Content, Custom Query)
• added to SPTableView the method setFont:
• fixed the initialisation of vars in CMTextView (fixes the displaying of create syntax)
|
|
|
|
| |
correct row count" preference with a new Table row counts query level (never, only for small tables, always), defaulting to only for small tables - boundary currently set to 5MB. This addresses Issue #500
|
|
|
|
| |
This completes the conversion of all constants in SPConstants to extern's.
|
| |
|
|
|
|
| |
toolbar identifiers, pasteboard drag types and file extensions.
|
|
|
|
|
|
| |
- status can be toggled by right-click in the text view and go to submenu "Spelling and Grammar" > "Check Spelling while Typing"
Note: up to now "Check Spelling while Typing" wont' be checked in the GUI if it's enabled → TODO (maybe related to the "sheet issue")
|
|
|
|
| |
this).
|
|
|
|
| |
consistent across all table views. Also includes live updating when the preference is changed as well as its implementation in the query console, process list and variables table views.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- New connection column (been meaning to add this for a while)
- Display table view column headers
- Enable table view text cell line truncating
- Allow table view columns to be re-ordered
- The table view now respects the display table view vertical grid lines preference
- Support for including the connection when saving messages to a file
- Support for showing/hiding the connection column
- Increase table view row height to match that of all others
- Display message time stamps using the user's system wide medium time format
|
|
|
|
|
|
|
|
| |
alt+cmd+P. Includes the ability to kill queries and connections as well as live filtering support and the ability to save all processes or the current filtered set to a file. Implements issue #458.
- Reorganise 'Database' menu.
- Give 'Flush Privileges' key equivalent of shift+cmd+F.
|
|
|
|
|
|
|
|
| |
- Improve task support on previously supported views
- Use a threaded task load for all initial table loads
- Support threaded task loads for table content loads, reloads, sorts, and filters
- Improve upon previous threaded task loads by minimising view updates and supporting updates of the existing data arrays where valid
|
|
|
|
| |
• Organize constants into groups
|
| |
|
|
|
|
|
|
|
|
|
| |
dump file
- this should simplify the loading of such a file in other text editors
- to avoid the writing of that BOM one can add to Sequel Pro's preference plist the boolean key “NoBOMforSQLdumpFile” and set it to YES
Note: If it turns out that this BOM causes problems one could add a checkbox for it to the NSSavePanel for instance later on.
|
|
|
|
| |
constant.
|
| |
|
|
|
|
|
|
|
|
|
| |
data loading:
- Removal of AMIndeterminateProgressIndicatorCell, and addition of a custom fork of YRKSpinningProgressIndicator which fixes bugs, adds threaded drawing, and adds a determinate mode.
- Addition of a task system within TableDocument, triggering display of a large central progress indicator and stopping the window from being interacted with in any way that would cause a query while the task is running.
- Add threaded TableContent content fetching, including use of the new task system and determinate progress bar; make fixes to improve threading stability and interaction.
|
|
|
|
| |
occurrences of it's use.
|
|
issues such as the one fixed in revision 1419. All future preference usage should be done so using these constants.
|