Write a Simple Go Application to work with AlloyDB Data on Linux

Go is an open source programming language that enables you to easily build software on Linux/UNIX machines. When Go is paired with the ODBC Driver for AlloyDB and unixODBC you are able write applications with connectivity to live AlloyDB data. This article will walk you through the process of installing the ODBC Driver for AlloyDB, configuring a connection using the unixODBC Driver Manager, and creating a simple Go application to work with AlloyDB data.

Using the CData ODBC Drivers on a Unix/Linux Machine

The CData ODBC Drivers are supported in various Red Hat-based and Debian-based systems, including Ubuntu, Debian, RHEL, CentOS, and Fedora. There are also several libraries and packages that are required, many of which may be installed by default, depending on your system. For more information on the supported versions of Linux operating systems and the required libraries, please refer to the "Getting Started" section in help documentation (installed and found online).

Installing the Driver Manager

Before installing the driver, you need to be sure that your system has a driver manager. For this article, you will use unixODBC, a free and open source ODBC driver manager that is widely supported.

For Debian-based systems like Ubuntu, you can install unixODBC with the APT package manager:

apt-get install unixodbc unixodbc-dev

For systems based on Red Hat Linux, you can install unixODBC with yum or dnf:

yum install unixODBC unixODBC-devel

The unixODBC driver manager reads information about drivers from an odbcinst.ini file and about data sources from an odbc.ini file. You can determine the location of the configuration files on your system by entering the following command into a terminal:

odbcinst -j

NOTE: You may need to install odbcinst. Use the following command in a terminal:

apt install odbcinst

The output of the command will display the locations of the configuration files for ODBC data sources and registered ODBC drivers. User data sources can only be accessed by the user account whose home folder the odbc.ini is located in. System data sources can be accessed by all users. Below is an example of the output of this command:

DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /home/myuser/.odbc.ini
SQLULEN Size.......: 8
SQLLEN Size........: 8
SQLSETPOSIROW Size.: 8

Installing the Driver

You can download the driver in standard package formats: the Debian .deb package format or the .rpm file format. Once you have downloaded the file, you can install the driver from the terminal.

The driver installer registers the driver with unixODBC and creates a system DSN, which can be used later in any tools or applications that support ODBC connectivity.

For Debian-based systems like Ubuntu, run the following command with sudo or as root:

dpkg -i /path/to/package.deb

For systems that support .rpms, run the following command with sudo or as root:

rpm -i /path/to/package.rpm

Once the driver is installed, you can list the registered drivers and defined data sources using the unixODBC driver manager:

List the Registered Driver(s)

odbcinst -q -d
CData ODBC Driver for AlloyDB
...

List the Defined Data Source(s)

odbcinst -q -s
CData AlloyDB Source
...

To use the CData ODBC Driver for AlloyDB with unixODBC, you need to ensure that the driver is configured to use UTF-16. To do so, edit the INI file for the driver (cdata.odbc.alloydb.ini), which can be found in the lib folder in the installation location (typically /opt/cdata/cdata-odbc-driver-for-alloydb), as follows:

cdata.odbc.alloydb.ini

...

[Driver]
DriverManagerEncoding = UTF-16

Modifying the DSN

When the driver is installed, a system DSN should be predefined. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties. Additionally, you can create user-specific DSNs that will not require root access to modify in $HOME/.odbc.ini.

The following connection properties are usually required in order to connect to AlloyDB.

• Server: The host name or IP of the server hosting the AlloyDB database.
• User: The user which will be used to authenticate with the AlloyDB server.
• Password: The password which will be used to authenticate with the AlloyDB server.

You can also optionally set the following:

• Database: The database to connect to when connecting to the AlloyDB Server. If this is not set, the user's default database will be used.
• Port: The port of the server hosting the AlloyDB database. This property is set to 5432 by default.

Authenticating with Standard Authentication

Standard authentication (using the user/password combination supplied earlier) is the default form of authentication.

No further action is required to leverage Standard Authentication to connect.

Authenticating with pg_hba.conf Auth Schemes

There are additional methods of authentication available which must be enabled in the pg_hba.conf file on the AlloyDB server.

Find instructions about authentication setup on the AlloyDB Server here.

Authenticating with MD5 Authentication

This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to md5.

Authenticating with SASL Authentication

This authentication method must be enabled by setting the auth-method in the pg_hba.conf file to scram-sha-256.

Authenticating with Kerberos

The authentication with Kerberos is initiated by AlloyDB Server when the ∏ is trying to connect to it. You should set up Kerberos on the AlloyDB Server to activate this authentication method. Once you have Kerberos authentication set up on the AlloyDB Server, see the Kerberos section of the help documentation for details on how to authenticate with Kerberos.

/etc/odbc.ini or $HOME/.odbc.ini

[CData AlloyDB Source]
Driver = /opt/cdata/cdata-odbc-driver-for-alloydb/lib/liballoydbodbc.x64.so
Description = My Description
User = alloydb
Password = admin
Database = alloydb
Server = 127.0.0.1
Port = 5432

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Creating a Simple Go App for AlloyDB Data

With the Driver Manager installed and the DSN configured, you are ready to create a simple Go application to work with your AlloyDB data. To start, install a Go driver for ODBC databases. While there are several options available, this article will use the odbc driver found at https://github.com/alexbrainman/odbc.

Installing ODBC on Linux

There are a series of steps required to install the ODBC driver for Go.

1. Create the $HOME/golang/go path (if it does not exist) by entering the following commands in a terminal:

   mkdir /root/golang
   mkdir /root/golang/go
    

2. Define the GOPATH environment variable:

   export GOPATH=$HOME/golang/go
    

3. Create a module inside the new Go directory:

   cd $GOPATH
   go mod init myproject
    

4. Install the Go driver for ODBC databases:

   go get http://github.com/alexbrainman/odbc
    

Now you are ready to create and execute a simple Go application.

Sample Go Application

The sample application issues a simple SQL SELECT query for AlloyDB data and displays the results. Create the directory $GOPATH/src/cdata-odbc-alloydb and create a new Go source file, copying the source code from below.

cdata-odbc-alloydb.go

package main

import (
 _ "github.com/alexbrainman/odbc"
 "database/sql"
 "log"
 "fmt"
)

func main() {
 db, err := sql.Open("odbc",
 "DSN=CData AlloyDB Source")
 if err != nil {
 log.Fatal(err)
 }

 var (
 shipname string
 shipcity string
 )

 rows, err := db.Query("SELECT ShipName, ShipCity FROM Orders WHERE ShipCountry = ?", "USA")
 if err != nil {
 log.Fatal(err)
 }
 defer rows.Close()
 for rows.Next() {
 err := rows.Scan(&shipname, &shipcity)
 if err != nil {
 log.Fatal(err)
 }
 fmt.Println(shipname, shipcity)
 }
 err = rows.Err()
 if err != nil {
 log.Fatal(err)
 }

 defer db.Close()
}

In the terminal, navigate to the Go application directory and build the application:

go build

After the application builds, you will be able to execute the application, displaying your AlloyDB data:

./cdata-odbc-alloydb

At this point, you have a simple Go application for working with AlloyDB data. From here, you can easily expand the application, adding deeper read/write functionality through familiar SQL queries.