| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
the current filtered result.
|
|
|
|
|
|
|
|
|
|
|
|
| |
- A new SPExportFile class, providing an abstract interface to the handling and creation of export files.
- Enables the centralisation of all file/file handle creation logic as well as better support for handling situations where files fail to be created, including files that already exist at the export location.
- New SPExportFileHandleStatus constants to support the reporting of file handle creation.
- Update SPExporter to use the new file class instead of directly using an instance of SPFileHandle.
- Add the necessary logic to deal with files that already exist on disk, by providing the user with 3 options: cancel the export, ignore the files in question or overwrite them. We might want to enhance this to make new files sequential in name to prevent overwriting. Fixes issue #742.
- New SPExportFileUtilities category, which centralises all the logic relating to writing export type headers as well as dealing with problems occurred during file/file handle creation.
- Improve feedback given on the export progress sheet during export initialisation.
- Tidy up and improve comments.
|
| |
|
|
|
|
| |
a new category SPExportFilenameUtilities.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
strings
- Tweak MySQL help search to include a localisable language code for results in requested languages
This addresses Issue #743
|
|
|
|
|
|
| |
- 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.
|
| |
|
|
|
|
|
|
|
| |
• further Save Session progress
- store "saved as session accessory view data" globally to support "Save Session"
- delete global "saved as session accessory view data" if last SP window will be closed
- added to info.plist which tab is currently selected
|
|
|
|
| |
multiple files.
|
|
|
|
|
|
|
| |
- Make sure the export button is disabled when the global structure, content and drop options are enabled, but the desellect all button is checked.
- Replace the export dialog toolbar with a tabview, reducing the dialogs overall size.
- Add the option to SQL dumps to specify when a new INSERT statement should be created, either after a certain amount of data or after a specific number of rows (defaults to every 250KiB). Known issue: incorrect VALUES clause generation of last row when creating a new INSERT after a specific number of rows.
|
|
|
|
|
|
|
| |
- Correctly disable exporting custom query results as SQL and enable for all other formats.
- Fix CSV exports when exporting from a source other than the selected tables.
- Correctly export custom query results instead of all tables as a result of a missing IB connection.
|
|
|
|
|
|
|
|
| |
- Move the custom filename options view to a drop down view on the main exporter dialog.
- Change the export data source matrix to a popup button.
- Fix the export button being enabled when no tables are selected to be exported.
- Various interface validation fixes.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Improve interface validation on the SQL view, including fixing no-content toggling
- Fix the export of views to correctly construct placeholder tables and fix view syntax export (this addresses Issue #707)
- Fix logic controlling Stored Procedure and Function export - fix hangs and allow correct export
- Handle permission errors when retrieving Stored Pro/Function syntax
- Improve export of linebreaks in CSV quoted cells for improved Excel compatibility
- SQL export now retrieves table syntax as it progresses through the tables - more accurate progress bar and removes initial pause when exporting lots of tables
- Alter filename construction to use centralised filename string: fixes end export Growl notification
- Improve dump comments
|
|
|
|
| |
exported NULL values. Fixes issue #718.
|
|
|
|
|
|
|
|
| |
those are enabled
- Exporter: SQL export now correctly excludes structure/drop table if the global structure/drop toggles are disabled
- Exporter: Save exporter window size
|
| |
|
| |
|
|
|
|
|
| |
- When compression is enabled, use .sql.gz as file extension instead of .gz
|
|
|
|
|
|
|
| |
- Fix the same potential autorelease pool memory leak found in the CSV exporter in the XML exporter.
- When performing an XML export to a single file don't write the header twice.
- Remember to append the .xml extension when performing an XML export to a single file.
|
|
Includes a completely redesign approach to all export data types based on the use of NSOperation subclasses. CSV, SQL, XML and dot export types are currently functional, while the source files for PDF and HTML export types exist they are to be implemented, but are currently hidden from the interface.
Also includes the following:
- Completely redesigned export interface.
- The ability to customize CSV NULL values.
- The ability to specify whether the UTF-8 BOM should be used in SQL dumps.
- The ability to specify whether BLOB fields are output as hex or plain text during SQL dumps. Defaults to hex.
- Exporting currently selected tables via the tables list context menu.
Outstanding issues:
- Not all progress indicators for all export types are functional (or functioning correctly).
- A few issues related to the introduction of only exporting the content and create and drop syntax of specific tables during SQL dumps.
Needs some serious testing and benchmarking to ensure it replicates the current export functionality.
|