The FreeBSD Ports Archive
FreeBSD databases : mysql2odbc4>
Openlink MySQL-ODBC Gateway
The MySQL-ODBC SDK enables you to make MySQL-specific applications
database-independent without wholesale re-writes of your application code.
Thus, applications that are written directly to the MySQL call level interface
now end up being database independent via iODBC (or unixODBC), and usable
against any ODBC accessible database (including MySQL).
http://www.iodbc.org/index.php?page=mysql2odbc/index
|
mysql2odbc history
v. 1.7
date: 2006/12/16 10:31:52; author: fjoe; state: Exp; lines: +1 -1
- Fix the build with gcc 4.1
- Bump PORTREVISION
v. 1.6
date: 2006/11/28 20:07:20; author: fjoe; state: Exp; lines: +1 -1
Bump PORTREVISION.
v. 1.5
date: 2006/11/28 19:48:18; author: fjoe; state: Exp; lines: +1 -1
Fix the build with unixODBC 2.2.12:
GNU_CONFIGURE= yes -> USE_AUTOTOOLS= libtool:15
Pointed out by: kris via pointyhat
v. 1.4
date: 2006/02/23 10:35:08; author: ade; state: Exp; lines: +0 -1
Conversion to a single libtool environment.
Approved by: portmgr (kris)
v. 1.3
date: 2005/09/13 11:42:15; author: fjoe; state: Exp; lines: +1 -1
Use BROKEN instead of ".error". This allows to run "make config" to
reconfigure the port properly.
v. 1.2
date: 2005/09/13 11:38:16; author: fjoe; state: Exp; lines: +9 -1
- Fix build on RELENG_4 [1]
- Fix build with iODBC
- Bump PORTREVISION
Found by: kris (via pointyhat) [1]
v. 1.1
date: 2005/08/31 18:43:34; author: fjoe; state: Exp;
New port: mysql2odbc 0.99.2
The MySQL-ODBC SDK enables you to make MySQL-specific applications
database-independent without wholesale re-writes of your application code.
Thus, applications that are written directly to the MySQL call level interface
now end up being database independent via iODBC (or unixODBC), and usable
against any ODBC accessible database (including MySQL).
WWW: http://www.iodbc.org/index.php?page=mysql2odbc/index
=============================================================================
|
| |

|