sequelpro/.git - MySQL/MariaDB database management for macOS

	Commit message (Collapse)	Author	Age	Files	Lines
*	When exporting either a filtered or custom query result include the query in ↵	stuconnolly	2010-11-07	1	-2/+8
\| \| \| \|	the opening resultset tag that produced the result.
*	Complete the implementation of supporting MySQL's XML schema format when ↵	stuconnolly	2010-11-05	1	-4/+7
\| \| \| \|	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 ↵	stuconnolly	2010-11-04	1	-1/+5
\| \| \| \|	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.
*	Localize the header included in SQL and XML exports.	stuconnolly	2010-10-19	1	-7/+7
\|
*	If the user chooses to overwrite the output file(s) when performing an ↵	stuconnolly	2010-08-26	1	-1/+10
\| \| \| \|	export make sure compression and CSV and XML headers and re-enable/rewritten.
*	Encoding changes and improvements, particularly to increase compatibility ↵	rowanbeentje	2010-08-25	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	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
*	• overall replacement of:	Bibiko	2010-08-20	1	-6/+6
\| \| \| \| \| \| \| \| \|	[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!
*	Fix release and dist builds.	stuconnolly	2010-08-16	1	-5/+3
\|
*	Various export enhancements and fixes, including:	stuconnolly	2010-08-12	1	-0/+212
	- 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.