2012-11-22 11:01:09 +01:00
|
|
|
# $NetBSD: options.mk,v 1.6 2012/11/22 10:01:10 jnemeth Exp $
|
2006-01-23 19:53:45 +01:00
|
|
|
|
|
|
|
|
PKG_OPTIONS_VAR= PKG_OPTIONS.myodbc
|
|
|
|
|
PKG_OPTIONS_REQUIRED_GROUPS= db
|
Changes 5.1.8:
* Documentation in .CHM and .HLP format has been removed from the distribution.
* For some procedure and parameter combinations SQLProcedureColumns() did not
work correctly. For example, it could not return records for an existing
procedure with correct parameters supplied.
* Further, it returned incorrect data for column 7, TYPE_NAME. For example, it
returned VARCHAR(20) instead of VARCHAR.
* The MySQL Connector/ODBC MSI installer did not set the InstallLocation value
in the Microsoft Windows registry.
* In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the
uploaded data contained errors, such as primary key duplication, and foreign
key violation.
* SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if
the query was parameterized and not all parameters were bound.
* Note, MSDN states that “For performance reasons, an application should not
call SQLColAttribute/SQLDescribeCol before executing a statement.” However,
it should still be possible to do so if performance reasons are not paramount.
* When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the
driver ran SET @@sql_select_limit=1, which limited the resultset to just one
row.
* After installing MySQL Connector/ODBC, the system DSN created could not be
configured or deleted. An error dialog was displayed, showing the error
message “Invalid attribute string”.
* In this case the problem was due to the fact that the driver could not parse
the NULL-separated connection string.
* When used after a call to SQLTables(), SQLRowCount() did not return the
correct value.
2011-08-19 09:59:58 +02:00
|
|
|
PKG_OPTIONS_GROUP.db= iodbc unixodbc
|
|
|
|
|
PKG_SUPPORTED_OPTIONS= gui
|
|
|
|
|
PKG_SUGGESTED_OPTIONS= iodbc
|
2006-01-23 19:53:45 +01:00
|
|
|
|
|
|
|
|
.include "../../mk/bsd.options.mk"
|
|
|
|
|
|
2008-04-13 00:42:57 +02:00
|
|
|
PLIST_VARS+= gui
|
|
|
|
|
|
Changes 5.1.8:
* Documentation in .CHM and .HLP format has been removed from the distribution.
* For some procedure and parameter combinations SQLProcedureColumns() did not
work correctly. For example, it could not return records for an existing
procedure with correct parameters supplied.
* Further, it returned incorrect data for column 7, TYPE_NAME. For example, it
returned VARCHAR(20) instead of VARCHAR.
* The MySQL Connector/ODBC MSI installer did not set the InstallLocation value
in the Microsoft Windows registry.
* In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the
uploaded data contained errors, such as primary key duplication, and foreign
key violation.
* SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if
the query was parameterized and not all parameters were bound.
* Note, MSDN states that “For performance reasons, an application should not
call SQLColAttribute/SQLDescribeCol before executing a statement.” However,
it should still be possible to do so if performance reasons are not paramount.
* When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the
driver ran SET @@sql_select_limit=1, which limited the resultset to just one
row.
* After installing MySQL Connector/ODBC, the system DSN created could not be
configured or deleted. An error dialog was displayed, showing the error
message “Invalid attribute string”.
* In this case the problem was due to the fact that the driver could not parse
the NULL-separated connection string.
* When used after a call to SQLTables(), SQLRowCount() did not return the
correct value.
2011-08-19 09:59:58 +02:00
|
|
|
.if !empty(PKG_OPTIONS:Mgui)
|
2006-01-23 19:53:45 +01:00
|
|
|
. include "../../x11/qt3-tools/buildlink3.mk"
|
2012-11-22 11:01:09 +01:00
|
|
|
#CONFIGURE_ARGS+= --enable-gui
|
|
|
|
|
#USE_LANGUAGES= c c++
|
2008-04-13 00:42:57 +02:00
|
|
|
PLIST.gui= yes
|
2006-01-23 19:53:45 +01:00
|
|
|
.else
|
2012-11-22 11:01:09 +01:00
|
|
|
#CONFIGURE_ARGS+= --disable-gui
|
2006-01-23 19:53:45 +01:00
|
|
|
.endif
|
|
|
|
|
|
Changes 5.1.8:
* Documentation in .CHM and .HLP format has been removed from the distribution.
* For some procedure and parameter combinations SQLProcedureColumns() did not
work correctly. For example, it could not return records for an existing
procedure with correct parameters supplied.
* Further, it returned incorrect data for column 7, TYPE_NAME. For example, it
returned VARCHAR(20) instead of VARCHAR.
* The MySQL Connector/ODBC MSI installer did not set the InstallLocation value
in the Microsoft Windows registry.
* In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the
uploaded data contained errors, such as primary key duplication, and foreign
key violation.
* SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if
the query was parameterized and not all parameters were bound.
* Note, MSDN states that “For performance reasons, an application should not
call SQLColAttribute/SQLDescribeCol before executing a statement.” However,
it should still be possible to do so if performance reasons are not paramount.
* When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the
driver ran SET @@sql_select_limit=1, which limited the resultset to just one
row.
* After installing MySQL Connector/ODBC, the system DSN created could not be
configured or deleted. An error dialog was displayed, showing the error
message “Invalid attribute string”.
* In this case the problem was due to the fact that the driver could not parse
the NULL-separated connection string.
* When used after a call to SQLTables(), SQLRowCount() did not return the
correct value.
2011-08-19 09:59:58 +02:00
|
|
|
.if !empty(PKG_OPTIONS:Miodbc)
|
2006-01-23 19:53:45 +01:00
|
|
|
. include "../../databases/iodbc/buildlink3.mk"
|
|
|
|
|
.endif
|
|
|
|
|
|
Changes 5.1.8:
* Documentation in .CHM and .HLP format has been removed from the distribution.
* For some procedure and parameter combinations SQLProcedureColumns() did not
work correctly. For example, it could not return records for an existing
procedure with correct parameters supplied.
* Further, it returned incorrect data for column 7, TYPE_NAME. For example, it
returned VARCHAR(20) instead of VARCHAR.
* The MySQL Connector/ODBC MSI installer did not set the InstallLocation value
in the Microsoft Windows registry.
* In bulk upload mode, SQLExecute would return SQL_SUCCESS, even when the
uploaded data contained errors, such as primary key duplication, and foreign
key violation.
* SQLDescribeCol and SQLColAttribute could not be called before SQLExecute, if
the query was parameterized and not all parameters were bound.
* Note, MSDN states that “For performance reasons, an application should not
call SQLColAttribute/SQLDescribeCol before executing a statement.” However,
it should still be possible to do so if performance reasons are not paramount.
* When SQLNumResultCols() was called between SQLPrepare() and SQLExecute() the
driver ran SET @@sql_select_limit=1, which limited the resultset to just one
row.
* After installing MySQL Connector/ODBC, the system DSN created could not be
configured or deleted. An error dialog was displayed, showing the error
message “Invalid attribute string”.
* In this case the problem was due to the fact that the driver could not parse
the NULL-separated connection string.
* When used after a call to SQLTables(), SQLRowCount() did not return the
correct value.
2011-08-19 09:59:58 +02:00
|
|
|
.if !empty(PKG_OPTIONS:Munixodbc)
|
2006-01-23 19:53:45 +01:00
|
|
|
. include "../../databases/unixodbc/buildlink3.mk"
|
2012-11-22 11:01:09 +01:00
|
|
|
CMAKE_ARGS+= -DWITH_UNIXODBC=1
|
2006-01-23 19:53:45 +01:00
|
|
|
.endif
|
