goracle/oracle is a package is a translated version of cx_Oracle (by Anthony Tuininga) converted from C (Python module) to Go.

goracle/godrv is a package which is a database/sql/driver.Driver compliant wrapper for goracle/oracle - passes github.com/bradfitz/go-sql-test (as github.com/tgulacsi/go-sql-test).

CHAR, VARCHAR2, NUMBER, DATETIME, INTERVAL simple AND array bind/define. CURSOR, CLOB, BLOB

Nothing I know of.

Nothing I know of.

LONG, LONG RAW, BFILE

I haven't had the pressure to force me understanding database/sql - yet. I've ported cx_Oracle because I'm using Python with Oracle most of, and no featureful OCI binding has existed for Go that time. Thus I'm fluent with cx_Oracle and that means goracle/oracle.

BUT I'd start and stick with database/sql as long as it is possible

• my impression is that Go's standard library is very high quality.

Of course if you need to use Oracle's non-standard features (out bind variables, returning cursors, sending and receiving PL/SQL associative tables...) then goracle/oracle is the straight choice.

For simple (connection, Ping, Select) usage, and testing connection (DSN can be tricky), see conntest.

You can build the test executable (for debugging with gdb, for example) with go test -c

You can build a tracing version with the "trace" build tag (go build -tags=trace) that will print out everything before calling OCI C functions.

See c for example.

It is go get'able iff you have Oracle DB installed OR the Oracle's InstantClient both the Basic Client and the SDK (for the header files), too!

• installed

For environment variables, you can try env

AND you have set proper environment variables:

export CGO_CFLAGS=-I$(dirname $(find $ORACLE_HOME -type f -name oci.h))
export CGO_LDFLAGS=-L$(dirname $(find $ORACLE_HOME -type f -name libclntsh.so\*))
go get github.com/tgulacsi/goracle

For example, with my XE:

ORACLE_HOME=/u01/app/oracle/product/11.2.0/xe
CGO_CFLAGS=-I/u01/app/oracle/product/11.2.0/xe/rdbms/public
CGO_LDFLAGS=-L/u01/app/oracle/product/11.2.0/xe/lib

With InstantClient:

CGO_CFLAGS=-I/usr/include/oracle/11.2/client64
CGO_LDFLAGS=-L/usr/include/oracle/11.2/client64

For Mac OS X I did the following:

You have to get both the Instant Client Package Basic and the Instant Client Package SDK (for the header files).

Then set the env vars as this (note the SDK here was unpacked into the base directory of the Basic package)

export CGO_CFLAGS=-I/Users/dfils/src/oracle/instantclient_11_2/sdk/include
export CGO_LDFLAGS=-L/Users/dfils/src/oracle/instantclient_11_2
export DYLD_LIBRARY_PATH=/Users/dfils/src/oracle/instantclient_11_2:$DYLD_LIBRARY_PATH

Perhaps this export would work too, but I did not try it. I understand this is another way to do this

export DYLD_FALLBACK_LIBRARY_PATH=/Users/dfils/src/oracle/instantclient_11_2

The DYLD vars are needed to run the binary, not to compile it.