aboutsummaryrefslogtreecommitdiffstats
path: root/Source/SPXMLExporterDelegate.m
Commit message (Collapse)AuthorAgeFilesLines
* Change Sequel Pro's license from GPL (version 2) to MIT.stuconnolly2012-07-251-13/+20
|
* Export tidy up.stuconnolly2012-05-251-12/+1
|
* - Clean up SPMySQL and QueryKit inclusion and search methods, which should ↵rowanbeentje2012-03-271-1/+1
| | | | | | | fix nightly builds - Fix warnings
* Warning: this branch commit is largely untested, and known to throw ↵rowanbeentje2012-02-231-0/+1
| | | | | | | | | | | | exceptions as database structure retrieval is currently missing! Further work on SPMySQLFramework integration: - Improve SPMySQL framework build settings including correct ppc builds and a Distribution configuration for the build distributions to match - Add new convenience querying and result methods to the framework - Amend Sequel Pro source to use the new SPMySQL.framework methods everywhere, replacing MCPKit methods where they differ and improving some functions - Remove MCPKit from the source - Fix a number of warnings on Release-style builds
* - Fix more compiler warningsrowanbeentje2011-03-151-1/+1
| | | | | - Tweak README
* Complete the implementation of supporting MySQL's XML schema format when ↵stuconnolly2010-11-051-3/+18
| | | | exporting. Also, restore our old format and give the user the choice during export (defaults to MySQL schema). Completes the implementation of issue #840.
* Start moving towards using the same XML format as MySQL uses. The inclusion ↵stuconnolly2010-11-041-4/+2
| | | | of the query executed for filtered and query results as well as the table structure when exporting entire tables still needs to be added. Part of issue #840.
* - Split out all of SPExportController's delegate methods to their own category.stuconnolly2010-10-241-2/+0
| | | | | | | | - Prepare for the implementation of PDF and HTML export by hiding the export options box for export types that don't need it. - Fix some spacing issues on the export dialog. - Create a new SPCategoryAdditions header that is included in the apps precompiled header, making all additions available to all classes. - Update strings files.
* Encoding changes and improvements, particularly to increase compatibility ↵rowanbeentje2010-08-251-2/+2
| | | | | | | | | | | with extended characters in MySQL identifiers (names of dbs/tables/cols): - Move encoding queries and control into MCPKit, with newly cleaned-up methods, and switch a number of locations to using the new code. - Use UTF8 connections for many identifier-based queries (selecting and listing databases, tables, stored procs, table information). This fixes selection and creation of table and database names containing extended characters, also fixing exceptions and errors. - Improve UTF8 over Latin1 to correctly set the client character set encoding as well, fixing custom queries and edits; remove custom code in SPTableContent achieving the same thing in a single location. - Fix database encoding detection routines - Update localisable strings
* Fix the display and updating of the export progress sheet when performing an ↵stuconnolly2010-08-141-8/+8
| | | | XML export. Caused by the incorrect implementation of XML export delegate methods as well as a missing call to one of them during the export process.
* Various export enhancements and fixes, including:stuconnolly2010-08-121-4/+4
| | | | | | | | | | | | - 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.
* In addition to Gzip compression support when exporting SQL dumps add the ↵stuconnolly2010-07-241-0/+1
| | | | | | | | | | | | | | | | | | 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.
* Rename TableDocument to SPDatabaseDocument.stuconnolly2010-05-281-1/+1
|
* Merge export redesign branch back into trunk.stuconnolly2010-05-241-0/+133
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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 21:26:07 +0000