aboutsummaryrefslogtreecommitdiffstats
path: root/Source/SPDotExporter.m
Commit message (Collapse)AuthorAgeFilesLines
* - Fix all the Xcode 4.6.2 build warnings, and tweak warning settings to ↵rowanbeentje2013-05-211-1/+1
| | | | enable some more
* * Composite Foreign Keys will now show all columns in Relation view (workaround)dmoagx2013-04-211-2/+2
|
* Remove useless init and dealloc method comments and perform general tidy up.stuconnolly2013-01-221-3/+2
|
* Change Sequel Pro's license from GPL (version 2) to MIT.stuconnolly2012-07-251-12/+19
|
* Fix more gcc warnings.stuconnolly2012-05-091-1/+1
|
* Ensure the that table constraints are cleared in [SPTableData ↵stuconnolly2011-10-081-7/+13
| | | | informationForTable:] to prevent the inclusion of them in subsequent calls for different tables. Fixes issue 1206.
* - Fix more compiler warningsrowanbeentje2011-03-151-1/+2
| | | | | - Tweak README
* Apply a tweaked version of a patch by Aaron Linville ↵rowanbeentje2010-12-051-2/+4
| | | | | | | | | | (http://www.linville.org/) to handle table linking in .dot exports on case-insensitive servers: - Adds a new checkbox on the .dot export interface controlling the case sensitivty of link handling - Improve .dot export to use lowercase link references when the option is enabled, fixing .dot exports of table relations of table names with uppercase characters on case-insensitive servers - Check the server's case-sensitivity setting and use that to control the checkbox when using the export interface to select .dot export This addresses Issue #920.
* - Fix graph language/DOT export hanging - this addresses Issue #916.rowanbeentje2010-12-021-32/+37
| | | | | | - Fix graph language/DOT export progress bars and feedback - Fix graph language/DOT export of table relations to correctly link tables based on foreign keys/constraints
* - Split out all of SPExportController's delegate methods to their own category.stuconnolly2010-10-241-1/+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.
* Considering nearly every class uses constants, import it via the prefix header.stuconnolly2010-10-191-1/+0
|
* • overall replacement of:Bibiko2010-08-201-19/+17
| | | | | | | | | [aString appendString:[NSString stringWithFormat:]] by [aString appendFormat:] since it's much more faster • first look at loop where several [aStr appendString:] occur to try to combine them into one appendString or appendFormat since the allocation of memory takes really time Note: I tested all my changes but we should test it further to be sure that I didn't a mistake!
* Various export enhancements and fixes, including:stuconnolly2010-08-121-4/+8
| | | | | | | | | | | | - 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.
* - Expose a number of help menu items and help buttons to use localisable ↵rowanbeentje2010-07-181-1/+1
| | | | | | | | strings - Tweak MySQL help search to include a localisable language code for results in requested languages This addresses Issue #743
* Fix various memory leaks as a result of static analysis.stuconnolly2010-07-061-0/+1
|
* Remove unsed try/catch exception blocks in all data exporters.stuconnolly2010-05-271-121/+118
|
* Merge export redesign branch back into trunk.stuconnolly2010-05-241-0/+227
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.