Commits
dimir authored 1c86b354f1c
...GI..PS. [ZBX-5386] fix ODBC items to become unsupported when NULL value returned Before this fix SQL queries of "Database monitor" items where not properly checked for: - empty result - NULL values In both cases an item became UNSUPPORTED (except for the null value for "Character" value type, which isn't probably correct) but the error message was provided only in case NULL value was received for Integer value type. An error message was: item [db.odbc.select[...]] became not supported: Received value [@?] is not suitable for value type [Numeric (unsigned)] and data type [Decimal] The @? is garbage. This fix adds handling of such situations. In both cases an item becomes unsupported no matter what value type it has. The error messages are respectively: - SQL query returned empty result. - SQL query returned NULL value. Also this fix improves configure check for unixODBC. Some GNU/Linux distributions have unixODBC packages without odbc_config binary, that you can use to get things needed to add support for unixODBC to your application. Before this fix when building Zabbix server with unixODBC support if odbc_config binary was missing configure would result in an error. This has been changed so that if odbc_config is missing we continue without additional CFLAGS and LDFLAGS with just additional -lodbc. On a Debian 6.0 this allowed successful compilation.