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

	Commit message (Collapse)	Author	Age	Files	Lines
*	- Fix a large memory leak in [MCPConnection prepareString]	rowanbeentje	2009-07-23	1	-1/+1
\|
*	Remove delegate calls asking for SP specific TableDocument ivars, replacing ↵	stuconnolly	2009-07-22	2	-7/+9
\| \| \| \|	them with more generic delegate methods.
*	- Allow the reconnection dialogs to function correctly if anything other ↵	rowanbeentje	2009-07-22	1	-4/+4
\| \| \| \| \| \| \|	than "Disconnect" is selected - Fix tunnel restarts
*	- Restore MySQL 3.x compatibility	rowanbeentje	2009-07-22	1	-3/+3
\|
*	To prevent a deadlock situation in fetchMaxAllowedPacket, query lock must be ↵	stuconnolly	2009-07-21	1	-1/+1
\| \| \| \|	unlocked as serverMajorVersion performs a query and thus attempts to obtain the lock.
*	Merge framework integration branch back to trunk. Summary of changes:	stuconnolly	2009-07-21	45	-0/+10483
	- Includes all custom code from subclasses CMMCPConnection and CMMCPResult, meaning they have subsequently been removed from the project. - All previous Sequel Pro specific code in the above subclasses has been removed in favour of the delegate (currently set to TableDocumet) informing the framework of such information. - All references to CMMCPConnection and CMMCPResult have subsequently been changed to MCPConnection and MCPResult. - Framework includes MySQL 5.1.36 client libraries and source headers. - Framework is now built as a 4-way (32/64 bit, i386/PPC arch) binary. - All import references to <MCPKit_bundled/MCPKit_bundled.h> have been changed to <MCPKit/MCPKit.h>. - New script 'build-mysql-client.sh' can be used to build the MySQL client libraries from the MySQL source. See the script's header for a list of available options or run it with no arguments to display it's usage. Note that there are still a few changes to be made to the framework with regard to removing Sequel Pro specific calls to the delegate. These however can be made later on as they have no effect on functionality and are merely design changes. Also, note that any future development done on the framework should be made to be as 'generic' as possible, with no Sequel Pro specific references. This should allow the framework to be integrated into another project without the need for SP specific code.