| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
• added SP's SPData/StringAdditions to QuickLook generator to avoid double-coding
• cleaned generator code a bit
|
|
|
|
| |
dependency
|
|
|
|
| |
window, including for single tabs in windows moved by their tabs
|
|
|
|
|
|
| |
- Fix toolbar issues when the last tab is dragged "out of" a window (eg a window is moved via the only tab left inside it)
- Fix window positioning flicker when dragging a tab out of its window
|
|
|
|
| |
indexes view labels
|
| |
|
|
|
|
| |
item localisable
|
|
|
|
| |
the storage range
|
|
|
|
|
|
|
| |
code; this addresses hangs (see Issue #6677) and also prevents triggering the discrete graphics chip on newer MacBook Pros.
- Update localisable strings
|
| |
|
|
|
|
|
|
|
|
| |
syntax to \n. This addresses Issue #652.
- Clean up SPSQLParser, and use a few more CFString methods to avoid obj-c messaging in loops
- When importing SQL using autodetect, perform a manual SET NAMES if possible to cope with poorly-exported files.
|
|
|
|
| |
code, in an attempt to fix Issue #677. It appears from testing that this is only a partial fix, but does reduce hang frequency.
|
|
|
|
| |
extension to be .tsv
|
|
|
|
| |
a new category SPExportFilenameUtilities.
|
|
|
|
|
|
|
|
|
|
|
| |
For example:
If either the table content or custom query editor views are active and there is data available, these options will be selected as the export source ('Filtered' or 'Query Result'). If either of these views are not active then the default source are the currently selected tables. If no tables are currently selected then all tables are checked. Note that in this instance the default export type is SQL where as in the case of filtered or query result export the default type is CSV.
Also remove some old export methods.
Related to issue #610.
|
|
|
|
|
| |
- Add controllable encoding support when importing CSV and SQL files, including a new default "Autodetect" option. Add UniversalDetector framework to support encoding autodetection. This should address Issue #720.
|
|
|
|
| |
when reading uncompressed files
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ability to use Bzip2 compression.
Other changes include:
+ Enable the use of export compression (Gzip and Bzip2) for all export formats.
+ Move the compression options in the export dialog to the 'Advanced' export settings view.
+ Simplify the setting of common exporter properties (e.g. the connection, use of compression).
+ Fix a potential memory leak in the dot exporter.
+ Update the data importer to recognise Bzip2 compressed files.
+ Fix several display issues on export dialog.
+ Restore the default .csv file extension of CSV exports.
+ Correctly update the default export filename when selecting a output compression type.
The addition of Bzip2 compression support implements issue #688.
|
| |
|
|
|
|
| |
the work started in r2201 and should address Issue #748.
|
|
|
|
|
|
|
|
| |
- Sheets now appear positioned underneath the tab bar if visible
- Tweak bottom corner drawing for a clearer outline, without highlight overlay
- Frontmost tab no longer displays server name in the tab
Also fix exception when right-clicking on an index to reset auto-increment.
|
|
|
|
|
|
|
|
|
| |
methods
- Improve error handling when the connecting dies during import (previous the sheet would stay open)
- Fix localised strings for error messages (label and text the wrong way round)
- Improve comments
|
| |
|
|
|
|
| |
utf8 (broken in r2325)
|
|
|
|
|
|
|
|
| |
strings
- Tweak MySQL help search to include a localisable language code for results in requested languages
This addresses Issue #743
|
|
|
|
|
|
|
| |
- Make the minimum index view size a little smaller
- Add a button to reveal the indexes subview when it is collapsed. This button is hidden when te index view is not collapsed.
This addresses Issue #746
|
|
|
|
| |
invisible empty autocomplete when no autocomplete matches are found
|
|
|
|
|
|
| |
- Don't forcibly include the table name if only exporting a single table, even if the multiple tables checkbox is ticked
- Fix additional _null files exported for Filtered Result exports when the multiple tables checkbox is ticked. Also addresses leaking write threads for those files.
|
|
|
|
| |
context menu by checking only the selecting tables. If no tables are selected all of them are checked by default (the same as before). Fixes issue #755.
|
|
|
|
|
|
|
|
|
| |
- Exporting BIT fields properly in SQL dumps using b'x' notation.
- Properly handling editing of BIT fields in both the content and custom query results views.
- Correctly display BIT fields in the content view, where binary values are zero-padded to the specified length of the field.
(Note, that the new BIT handling logic has only been added to MCPKit's MCPStreamingResult and MCPResult as the latter does not keep a record of the field's length which the new functionality depends on. Needs to be discussed).
|
|
|
|
| |
queries. This addresses Issue #762.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
attempt, as well as improved handling of networks not present. This addresses Issue #657.
In MCPKit:
- Disable MySQL automatic reconnection, and add our own reconnection code for greater consistency
- If no network is available, delay reconnects by a short period to allow the network to come back up
- Improved handling of proxy disconnects
In SPSSHTunnel:
- Improved handling of SSH tunnel disconnects, improving automatic reconnection via MCPKit and fixing potential memory/logic tramping.
Also remove the "Retry" button from the Disconnected dialog, leaving only the choices "Reconnect" or "Disconnect".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
pops up
with all the fields prepopulated.
Edit works as 'DROP' old trigger and then 'CREATE' new trigger (since MySQL doesn't
have support for 'ALTER' trigger).
In case of error while adding the new trigger, when you add a new trigger, all the
info from the original trigger is preserved. (Don't know if this is the best solution).
|
|
|
|
| |
location of exports, change the search domain to NSAllDomainsMask to accommodate home directories which are not on the startup volume.
|
|
|
|
| |
the window has drawn. This addresses odd Exposé artifacts when first setup (Issue #758), as well as toolbar drawing issues when a tab is dragged into a new window.
|
|
|
|
| |
append a file extension for CSV exports.
|
|
|
|
| |
created when performing an SQL dump, replace the use of stringWithFormat: with appendString: for a potential speed improvement.
|
|
|
|
|
|
|
| |
collapse via code which was originally causing the problem. Also apply the same fix to SPCustomQuery.m.
(Note that this also identifies a probable cause of views going slightly out-of-view if views are collapsed and expanded a lot - the autoResizesSubviews property is disabled and re-enabled in BWToolKit surrounding a collapse, but this is done using a timer with the exact time interval as the corresponding collapse/expand frame resize. This sets up a race condition, where if the timer fires before the animation completes, the internal view will be slightly clipped. May require a BWToolKit fix)
|
|
|
|
| |
progress indicator to indicate that it's connecting in the event that the user switches to a different tab. Also preserve the tab's label as 'Connecting...' when switching tabs.
|
|
|
|
| |
accidently committed in r2426.
|
|
|
|
| |
Procs, or Funcs (maybe it's needed to improve the display or to skip it)
|
|
|
|
| |
textfields in Table Status view
|
| |
|
|
|
|
|
|
|
| |
• resized GUI elements (Run Current, Last Error Mes.) for localisation
• centered label for "Query Favorites" and "Query History"
- maybe we should think about the appearance these buttons!
• increased the min width of Custom Query view by 15px in order to avoid GUI overlappings
|
|
|
|
|
|
| |
Information that the view wasn't displayed correctly after opening
- the point is here probably a bug in BWToolkit that the collapsable subview forgets its setting for "setAutoresizesSubviews:YES" after collapsing
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
- Add a 'gear menu' with the option to export the current result set as either CSV or XML.
(Note, that the collapsiable view currently suffers from the same BWToolKit issue as the table information pane).
|
|
|
|
| |
compatibility; this corrects the "fix" in r2422, and addresses Issue #757
|