aboutsummaryrefslogtreecommitdiffstats
path: root/Source/SPSQLExporter.m
Commit message (Collapse)AuthorAgeFilesLines
* - 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
* Improve handling of BIT fields, including:stuconnolly2010-07-151-3/+8
| | | | | | | | | - 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).
* Given that the user can now decide how often a new INSERT statement is ↵stuconnolly2010-07-081-2/+6
| | | | created when performing an SQL dump, replace the use of stringWithFormat: with appendString: for a potential speed improvement.
* Fix various memory leaks as a result of static analysis.stuconnolly2010-07-061-3/+3
|
* - Fix SQLexporter known issue from r2311, and fix compilation against the ↵rowanbeentje2010-06-131-2/+2
| | | | 10.5 SDK
* Exporter ehancements:stuconnolly2010-06-131-12/+21
| | | | | | | - 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.
* A number of exporter improvements:rowanbeentje2010-06-071-69/+97
| | | | | | | | | | | | - 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
* Remove multiple occurrences of accessing the same array element, improving ↵stuconnolly2010-05-271-6/+8
| | | | the overall performance of SQL dumps.
* Rename TablesList to SPTablesList.stuconnolly2010-05-271-1/+1
|
* - Fix SQL export progress displayrowanbeentje2010-05-271-507/+503
| | | | | - When compression is enabled, use .sql.gz as file extension instead of .gz
* Merge export redesign branch back into trunk.stuconnolly2010-05-241-2/+770
| | | | | | | | | | | | | | | | | | | | | 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.
* More export redesign work. CSV data generation is currently working using ↵stuconnolly2009-10-061-0/+18
| | | | the old non-streaming code, but does not yet write to any files. Please note that this is still very much a work in progress.
* Some more data exporter redesign changes I've been meaning to commit.stuconnolly2009-09-161-16/+0
|
* More data export work.stuconnolly2009-08-291-0/+46