iODBC | source ODBC driver manager and SDK | Database library

by openlink C Version: v3.52.15 License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | iODBC Summary

iODBC is a C library typically used in Database applications. iODBC has no bugs, it has no vulnerabilities and it has low support. However iODBC has a Non-SPDX License. You can download it from GitHub.

Welcome to the iODBC driver manager maintained by OpenLink Software. This kit will provide you with everything you need in order to develop ODBC-compliant applications under Unix without having to pay royalties to other parties.

Support

Quality

Security

License

Reuse

Support

iODBC has a low active ecosystem.

It has 139 star(s) with 48 fork(s). There are 29 watchers for this library.

It had no major release in the last 12 months.

There are 15 open issues and 48 have been closed. On average issues are closed in 434 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of iODBC is v3.52.15

Quality

iODBC has no bugs reported.

Security

iODBC has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

iODBC has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

iODBC releases are available to install and integrate.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of iODBC

Get all kandi verified functions for this library.

iODBC Key Features

No Key Features are available at this moment for iODBC.

iODBC Examples and Code Snippets

No Code Snippets are available at this moment for iODBC.

Community Discussions

Trending Discussions on iODBC

Stata is not seeing environment variables needed for ODBC connection

How do I install RODBC so that is uses unixODBC?

RODBC on macOS Catalina

Connect to MS SQL Server Database Using isql on Mac

Loading huge tables with `INSERT INTO test VALUES` in MonetDBLite

How to build pyodbc with links to iODBC in macOS?

Debugging 'terminate called after throwing an instance of ...', when the exception _should_ have been caught

Error while rebuilding PHP 7 to add ODBC extension MacOS 10.13 (High Sierra): Makefile is not as expected

Configure errors

HortonWorks “Table or view not found” when querying Hive from Excel using ODBC connection in Mac

QUESTION

Stata is not seeing environment variables needed for ODBC connection

Asked 2021-May-15 at 06:35

I use the Simba ODBC driver (2.3.2) to connect Stata to BigQuery from my macOS laptop. I recently upgraded to Big Sur (11.2.1) and lost the ability to do this.

I am using iODBC and I am able to test the DSN successfully. I was also able to get everything to work in macOS 10.15.7 just fine (on a different machine).

The problem appears to be that Stata is not seeing the DYLD_LIBRARY_PATH environment variable that I have defined in my .bash_profile profile according to the driver configuration instructions.

In Stata, I get this error:

...

ANSWER

Answered 2021-Apr-26 at 21:50

To fix this, you need to disable SIP, which keeps the $DYLD_LIBRARY_PATH environment variable from being defined without issuing a warning.

To disable SIP:

Restart your computer in Recovery mode by holding down Command(⌘)-R once it powers off. Press that until you see the Apple icon and a progress bar.
From the Utilities menu, select Terminal.
At the prompt, type the following command and then press return: csrutil disable
Terminal should display a message that SIP was disabled.
From the Apple menu, select Restart.

Now you need to define an environment variable that points to the folder with libiodbc.dylib. To figure out where that folder is, type this in Terminal:

find / -name libiodbc.dylib 2>&1 | grep -v "find: "

Using your favorite text editor (like pico, emacs, or vi), you need to edit your .zshenv file. Open this file (or create it if it does not exist) with

pico ~/.zshenv

Using the first folder from above, define an environment variable by typing this in the file:

export DYLD_LIBRARY_PATH=$DYLD_LIBRARY_PATH:

Save and exit the text editor.

To apply the changes to the current shell, type source .zshenv.

This should make Stata and BQ play nice again.

zsh is the default shell starting with Catalina, so if you use another shell, you should modify things accordingly. I use bash myself, but I hope my translation for zsh works.

You may need to start Stata from the command line for this to fully work. Here's the output of the command after the fix above:

Source https://stackoverflow.com/questions/66233373

QUESTION

How do I install RODBC so that is uses unixODBC?

Asked 2019-Nov-15 at 16:05

After installing and configuring FreeTDS and unixODBC and confirming they are working correctly, I am trying to configure RODBC. However, I am getting the following results when attempting to view the ODBC data sources in the R console.

...

ANSWER

Answered 2017-Nov-02 at 14:22

Turns out the default RODBC package install won't work with unixODBC. Here is a process for recompiling and installing RODBC.

Remove current generic RODBC package via the R console.

Source https://stackoverflow.com/questions/47077493

QUESTION

RODBC on macOS Catalina

Asked 2019-Nov-08 at 20:53

I'm having trouble getting RODBC to work on macOS Catalina. I'm trying to connect to MS SQL Server. I have installed unixODBC using Homebrew and installed the Microsoft ODBC drivers from here. RODBC installs fine, and I installed it using this as suggested elsewhere:

install.packages('RODBC', type="source", configure.args='--with-odbc-include=/usr/local/lib' )

But when I run this:

RODBC::odbcDriverConnect(connection = "driver={ODBC Driver 17 for SQL Server};server=XYZ;database=XYZ;UID=XYZ;PWD=XYZ")

it hangs -- I have to cancel the command, and then I get a bunch of warnings that look like this:

[RODBC] ERROR: state IM003, code 0, message [iODBC][Driver Manager]Specified driver could not be loaded

I know that the SQL Server driver is installed, since using the ODBC package in R works -- with the same driver! But for some reason RODBC is using iODBC, and is apparently looking in the wrong place for the driver.

I'm trying to write code that will run on different platforms, and I've successfully used RODBC on Ubuntu and Windows. But I'm having a tough time figuring out how to get RODBC to work on my MacBook.

...

ANSWER

Answered 2019-Nov-08 at 20:53

I had the same issue connecting with Impala on Mac after some upgrades. The workaround was to make sure RODBC used unixodbc instead of iODBC as follows:

install unixodbc. I used brew.
Remove RODBC with remove.packages("RODBC")
Reinstall RODBC from source and specify the path to unixodbc lib and include with install.packages("RODBC", type = "source", configure.args = c("--with-odbc-include=/usr/local/include/","--with-odbc-lib=/usr/local/lib/") )

On my computer unixodbc is in /usr/local

Source https://stackoverflow.com/questions/58453678

QUESTION

Connect to MS SQL Server Database Using isql on Mac

Asked 2019-Aug-26 at 19:22

Summary: tsql connects and isql doesn't.

Details: I have tried every official installation guide and Stack Overflow question I can find, but none of them produce joy. I'm trying to connect to a MS SQL Server database from my Mac (Mohave), and ultimately a Xubuntu 16.04 virtual machine as well, using pyodbc. Before getting into the Python, I just want to trouble-shoot the connection. The problem is, most of the documentation I'm seeing is missing important details such as, "Should I use quotes in usernames and passwords?" Or, "Should I include the domain in the username?" And if I should include the domain the username, "Should I escape the backslash character?"

Here is my current setup: tsql -C produces

...

ANSWER

Answered 2019-Aug-26 at 19:22

Have you tried connecting after using the fully qualified domain name (fqdn) for your SQL Server in the freetds.conf file:

Source https://stackoverflow.com/questions/57662838

QUESTION

Loading huge tables with `INSERT INTO test VALUES` in MonetDBLite

Asked 2019-Mar-28 at 18:44

In my use case I'm generating data at runtime, and the cost of serializing such data into a CSV file and then loading to MonetDBLite using COPY will be potentially greater than using something like INSERT INTO tablename VALUES. Given that MonetDBLite does not use DBConnections as in ODBC/iODBC, does that mean that I do not need to clear the memory using explicit COMMIT statements, or do I still need to run COMMIT after loading some GB of data into a table in order not to occupy all the available primary memory? Thanks in advance.

...

ANSWER

Answered 2019-Mar-28 at 18:44

Which MonetDBLite are you using? You can use from-memory appends for very fast data loading in this case I think. For R/Python, we can directly append from data frames, for C the process is a little less convenient.

Source https://stackoverflow.com/questions/55404583

QUESTION

How to build pyodbc with links to iODBC in macOS?

Asked 2018-May-11 at 20:29

In Driver for pyodbc: how to specify its location in macOS?, TallTed suggested to open question to explain the following

Build pyodbc with links to iODBC (not its default of UnixODBC, which is not typical for macOS).

so now with the focus —

How can I build pyodbc with links to iODBC (not its default of UnixODBC, which is not typical for macOS)?

...

ANSWER

Answered 2018-May-11 at 20:29

This should/might work in 4.0.23, as it was the way it was done up to pyodbc v3.0.7:

First, in the file 'setup.py' change line 165 from:

Source https://stackoverflow.com/questions/48084708

QUESTION

Debugging 'terminate called after throwing an instance of ...', when the exception _should_ have been caught

Asked 2018-Apr-09 at 11:31

I'm debugging an issue which only seems to happen on Solaris (we test on Windows, Linux, OSX, Solaris, HP-UX, and AIX).

Our code throws an exception (which is totally expected), and this results in the 'terminate called after throwing an instance of ...' message being printed, and the process being terminated.

...

ANSWER

Answered 2018-Apr-05 at 14:35

I'm of course a bit guessing in the blue here, and thus this is half-answer half-comment, but exceptions not being caught even if they should sounds a lot like an ABI issue.

Do you compile all libraries and executables working together here with the same compiler? This includes libraries like the C++ standard library!

This answer says that loading a shared library which is built with GCC won't work in an executable built with Solaris Studio, unless you built that executable with Solaris 12.4 or newer and enabled C++11 support via -std=c++11.

Thus an immediate "fix" would be to change / check the compile flags of the executable which loads that shared library with the offending code.

Another difference between the executable and the shared library could be that one is configured for "setjmp/longjmp" exceptions and the other is not. _GLIBCPP_SJLJ_EXCEPTIONS in eh_throw.cc and in some config I found online.

Mention of the different exception handling strategies in GCC docs.

Source https://stackoverflow.com/questions/49658814

QUESTION

Error while rebuilding PHP 7 to add ODBC extension MacOS 10.13 (High Sierra): Makefile is not as expected

Asked 2018-Apr-09 at 11:09

I'm currently struggling with an issue with ODBC. I need to use odbc to connect with a FileMaker database.

I've set up a VM with MacOS High Sierra + Apache + MySQL + Php7 and I've already installed ODBC Manager (from ActualTech) + FileMaker ODBC driver.

My web-app is a copy from a previous project hosted on a MacOS 10.8. On MacOS 10.8 everything goes fine. But on new High Sierra I get this error

Call to undefined function odbc_connect()

I'm using CodeIgniter as PhP framework, but I think error may be related to PhP version since it looks like PhP does not recognize this method as its own.

I've read on PhP official web site that odbc_connect is fully compatible with PHP v7.

Even though, I cannot figure out why I get this error.

Is it related to new MacOS versions (it seems it has been removed ODBC Support on earlier OSX, as you can read here)?

Plus, I found out some articles that suggest to re-build PHP from source, adding this ODBC support manually. Should I go this way? I'm not fully sure I can go with this solution.

UPDATE (I'm rebuilding PHP from source)

I e-mailed to acutaltech support and they suggested me to follow instructions here http://www.iodbc.org/dataspace/doc/iodbc/wiki/iodbcWiki/IODBCPHPHOWTOMacOSX. So I'm trying to compile and build PHP on my own, but my Makefile does not contain anything about ODBC.

This is my Makefile

...

ANSWER

Answered 2018-Apr-09 at 11:09

Solved

I could not build my own PHP version with ODBC. To everyone having this issue I solved by using PHP-OSX, that's basically a PHP version customized with all extensions needed, already built. You can download the binary file here https://php-osx.liip.ch.

Hope this helps!

Source https://stackoverflow.com/questions/49570829

QUESTION

Configure errors

Asked 2018-Apr-01 at 08:20

Mac OS X

I do configure and then make my odbc binary.

That is configure command:

...

ANSWER

Answered 2018-Apr-01 at 08:20

The one of reasons is: the macro PGAC_ARG_REQ and some other were undefined, I have found the *.m4, copied and it works.

Thanks l'L'l for the great help!

Source https://stackoverflow.com/questions/49584583

QUESTION

HortonWorks “Table or view not found” when querying Hive from Excel using ODBC connection in Mac

Asked 2017-Oct-16 at 12:20

I am using Hortonworks sandbox 2.1 with Apache Hive ODBC driver 2.1 and iODBC.

The ODBC connection is successful when I test it using the iODBC software. But, when I open excel and use Microsoft query to return the data to excel spreadsheet I get this error when I run SQL SELECT query

: [Hortonworks][SQLEngine] (31740) Table or view not found: HIVE.default.tweetsbi.

I am able to view the tables inside the database, but I can't view the content of them. Whenever I press Run I get the aforementioned error.

I am getting the same error in both Excel 2011 and 2016

...

ANSWER

Answered 2017-Sep-28 at 12:46

I've got it to work by :

Editing the configuration of Hortonworks Hive ODBC Driver by changing UseNativeQuery from 0 to 1.
Give permission to the user "sandbox"

Source https://stackoverflow.com/questions/46390062

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install iODBC

You probably already unpacked this distribution. The next step is to make sure that your applications can find all the dynamic link libraries. Depending on your system's implementation of dynamic link libraries, you have a number of options:. If your system has a C compiler, you can verify the installation by compiling the iodbctest program. Otherwise, you may have ODBC applications installed on your system which you can use.
Install the libraries in a directory that is searched by your linker by default. Typical locations are /usr/lib and /usr/local/lib.
Install the libraries in some other place, and make sure that the environment variable your dynamic linker uses to find extra locations for dynamic link libraries. Most systems use the environment variable LD_LIBRARY_PATH to this end. Exceptions are AIX which uses LIBPATH and HP/UX which uses SHLIB_PATH.
Mac OS X users should read the separate README_MACOSX document for more detail of porting on this platform. Otherwise:. The configure program will examine your system for various compiler flags, system options etc. In some cases extra flags need to be added for the C compiler to work properly.

Support

While not mandated by the BSD license, any patches you make to the iODBC project may be contributed back into the project at your discretion. Contributions will benefit the Open Source and Data Access community as a whole. Submissions may be made via the iODBC Github project or via email to iodbc@openlinksw.com.

Find more information at: