Free mysql injection software for mac

MySQL Connector/ODBC (with MyODBC as acronym) allows you to connect to a MySQL database server using the ODBC database API on all Microsoft Windows and most Unix platforms, including through such applications and programming environments such as Microsoft.

Main features:
Standards compliant:
- The production-ready version of Connector/ODBC is compliant with the ODBC 2.50 specification, Level 0 (with some Level 1 and 2 features). The stable version, is compliant with the ODBC 3.51 specification, Level 1 (complete Core API and Level 2 features).
Cross-platform:
- Connector/ODBC is available for Microsoft Windows, as well as many Unix systems (including Linux, Sun Solaris, HP-UX, IBM AIX, and Mac OS X).

Enhancements
Functionality added or changed:
- Added FLAG_NO_BINARY_RESULT connection option to always handle binary function results as character data. (Bug #29402)
Bugs fixed:
- Some catalog functions used fixed-sized buffers for handling arguments that could be overrun, and misinterpreted some arguments as patterns when they should be treated as identifiers. (Bug #36275)
- SQLDriverConnect() returned SQL_ERROR when the user cancelled the dialog box instead of SQL_NO_DATA. (Bug #36293)
- System DSN lookup (using ODBC_BOTH_DSN) fails on Windows XP. (Bug #36203)
- SQLProcedures() followed by SQLFreeStmt() crashes (Bug #36069)
- ADO adUseServer cursor is lost after updating adLongVarWChar field (Bug #26950)
- SQL_TYPE_TIMESTAMP and SQL_TYPE_TIME parameters were incorrectly included when parameters were expanded. (Bug #37342)
- DSN-less connection prompting cannot lookup driver entry (Bug #37254)

MySQL GUI Tools 5.0-r12 MySQL offers an effective solution for administering your MySQL environment and gain significantly better visibility into how your databases are operating. Moreover, it is a freeware.

Major Features:

1. Integrate database management and maintenance into a single, seamless environment
2. Have clear and intuitive graphical user interface.
   

Requirements: Mac OS X 10.3.9 or later MySQL 4.0 or later

MySQL is a very popular and open source SQL database provided by MySQL AB. MySQL AB is a commercial company that builds its business providing services around the MySQL database.
MySQL is the worlds most popular open source database software, with over 100 million copies of its software downloaded or distributed throughout its history.
With superior speed, reliability, and ease of use, MySQL has become the preferred choice of corporate IT Managers because it eliminates the major problems associated with downtime, maintenance, administration and support.
MySQL is a key part of LAMP (Linux, Apache, MySQL, PHP / Perl / Python), the fast growing open source enterprise software stack.
More and more companies are using LAMP as an alternative to expensive proprietary software stacks because of its lower cost and freedom from lock-in.

Enhancements
- Replication: Important Note: Binary logging with --binlog_format=ROW failed when a change to be logged included more than 251 columns. This issue was not known to occur with mixed-format or statement-based logging. (Bug#42977)
- Replication: Assigning an invalid directory for the --slave-load-tmpdir caused the replication slave to crash. (Bug#42861)
- Replication: The mysql.procs_priv system table was not replicated. (Bug#42217)
- Replication: An INSERT DELAYED into a TIMESTAMP column issued concurrently with a an insert on the same column not using DELAYED, but applied after the other insert, was logged using the same timestamp as generated by the other (non-DELAYED) insert. (Bug#41719)
- Replication: The MIXED binary logging format did not switch to row-based mode for statements containing the LOAD_FILE() function. (Bug#39701)
- Replication: When the server SQL mode included IGNORE_SPACE, statement-based replication of LOAD DATA INFILE ... INTO tbl_name failed because the statement was read incorrectly from the binary log; a trailing space was omitted, causing the statement to fail with a syntax error when run on the slave. (Bug#22504)
- An attempt by a user who did not have the SUPER privilege to kill a system thread could cause a server crash. (Bug#43748)
- On Windows, incorrectly specified link dependencies in CMakeLists.txt resulted in link errors for mysql_embedded, mysqltest_embedded, and mysql_client_test_embedded. (Bug#43715)
- mysql crashed if a request for the current database name returned an empty result, such as after the client has executed a preceding SET sql_select_limit=0 statement. (Bug#43254)
- If the value of the version_comment system variable was too long, the mysql client displayed a truncated startup message. (Bug#43153)
Queries of the following form returned an empty result:
- SELECT ... WHERE ... (col=col AND col=col) OR ... (false expression)
- The strings/CHARSET_INFO.txt file was not included in source distributions. (Bug#42937)
- A dangling pointer in mysys/my_error.c could lead to client crashes. (Bug#42675)
- Passing an unknown time zone specification to CONVERT_TZ() resulted in a memory leak. (Bug#42502)
- With more than two arguments, LEAST(), GREATEST(), and CASE could unnecessarily return Illegal mix of collations errors. (Bug#41627)
- The mysql client could misinterpret its input if a line was longer than an internal buffer. (Bug#41486)
- In the help command output displayed by mysql, the description for the c (clear) command was misleading. (Bug#41268)
- The load_defaults(), my_search_option_files() and my_print_default_files() functions in the C client library were subject to a race condition in multi-threaded operation. (Bug#40552)
- If --basedir was specified, mysqld_safe did not use it when attempting to locate my_print_defaults. (Bug#39326)
- When MySQL was configured with the --with-max-indexes=128 option, mysqld crashed. (Bug#36751)
- Setting the join_buffer_size variable to its minimum value produced spurious warnings. (Bug#36446)
- The use of NAME_CONST() can result in a problem for CREATE TABLE ... SELECT statements when the source column expressions refer to local variables. Converting these references to NAME_CONST() expressions can result in column names that are different on the master and slave servers, or names that are too long to be legal column identifiers. A workaround is to supply aliases for columns that refer to local variables. Now a warning is issued in such cases that indicate possible problems. (Bug#35383)
- An attempt to check or repair an ARCHIVE table that had been subjected to a server crash returned a 144 internal error. The data appeared to be irrecoverable. (Bug#32880)
- The Time column for SHOW PROCESSLIST output and the value of the TIME column of the INFORMATION_SCHEMA.PROCESSLIST table now can have negative values. Previously, the column was unsigned and negative values were displayed incorrectly as large positive values. Negative values can occur if a thread alters the time into the future with SET TIMESTAMP = value or the thread is executing on a slave and processing events from a master that has its clock set ahead of the slave. (Bug#22047)
- Restoring a mysqldump dump file containing FEDERATED tables failed because the file contained the data for the table. Now only the table definition is dumped (because the data is located elsewhere). (Bug#21360)