GitHub ODBC 8.0.0 Windows
- Last Updated: May 8, 2026
- 12 minute read
- OpenAccess SDK
- Documentation
README
Progress(R) DataDirect(R)
Progress(R) DataDirect(R) for ODBC for GitHub(TM)
Windows Platforms (32- and 64-bit)
8.0.0 Release
February 2026
***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its
subsidiaries or affiliates. All Rights Reserved.
***********************************************************************
CONTENTS
Post-GA Product Announcements
Installation Directory
Requirements
Data Source and Platform Support
Changes Since 8.0.0
Release 8.0.0 Features
DataDirect ODBC Driver Configuration Manager
Notes, Known Problems, and Restrictions
Driver Workaround Options
Documentation
Installed Files for 32-bit Drivers
Installed Files for 64-bit Drivers
Post-GA Product Announcements
The readme files will no longer be updated with product announcements and new
features after the General Availability (GA) of the product. For the latest
updates and enhancements, please refer to the release notes
(https://www.progress.com/datadirect-connectors/whats-new).
Installation Directory
* The default installation directory for the 32-bit driver on a 64-bit
system is:
C:\Program Files (x86)\Progress\DataDirect\ODBC
* The default installation directory for all other installations is:
C:\Program Files\Progress\DataDirect\ODBC
Requirements
* The installer program requires a JVM that is Java SE 11 or higher, including
Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
* The driver requires a Java Virtual Machine (JVM): Java SE, version 8 or
higher, including Oracle JDK, OpenJDK, IBM SDK (Java), or higher
LTS versions.
* IMPORTANT: You must have the Microsoft Data Access Components (MDAC)
installed to use this product.
- For 32-bit Windows systems, version 2.6 or higher is required.
- For 64-bit Windows systems, version 2.8 or higher is required.
Depending on the version of your Windows operating system, these
components may already be installed. You can download a utility that
determines whether MDAC is installed and its version from the following
Microsoft site:
http://msdn.microsoft.com/en-us/data/aa937730.aspx
You can also download MDAC from the same site.
Data Source and Platform Support
For the latest data source and platform support information, refer to the
Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
Changes Since 8.0.0
CVE-2022-41853 - Use of Externally-Controlled Input to Select Classes or Code
('Unsafe Reflection')
-----------------------------------------------------------------------------
Several Progress DataDirect ODBC drivers utilized a version of HyperSQL
Database that was vulnerable to remote code execution described in
CVE-2022-41853. All impacted drivers have been patched to fix this
vulnerability. For details on impacted drivers and fixed versions, refer to
the following KB article:
https://community.progress.com/s/article/DataDirect-ODBC-Critical-Security-
Bulletin-November-2022-CVE-2022-41853
Enhancements
------------
* The driver is now compiled with a Visual Studio 2022 compiler for Windows
platforms. As a result, you must have Microsoft Visual C/C++ runtime
version 14.40.33810 or higher on your machine to run the driver.
* The ICU library files that are installed with the product have been
upgraded to version 74.1. As a part of this upgrade, the ICU library
file names have changed:
- For the 32-bit driver: From ivicu28.dll to ivicu.dll
- For the 64-bit driver: From ddicu28.dll to ddicu.dll
This upgrade is available starting in build 08.02.1072 of the ICU
library files.
* The installer program has been enhanced to support Azul Zulu JRE 11.
As a result of this change, the installer has ended support for platforms
that do not support Java SE 8 or higher. The installer supports the following
operating systems after the enhancement:
* Windows:
- Windows 8.1 or higher
- Windows Server 2012 RC2 or higher
Important: These changes do not affect the operating system requirements of
the driver.
* The driver has been enhanced to support the Bearer token authentication.
See "Bearer token authentication" in the "Notes, Known Problems, and
Restrictions" section for details.
Changed Behavior
----------------
* The installer program now requires you to install a JRE that is Java SE 11 or
higher before running the installer. In earlier versions, the JRE used by the
installer program was included in the product. However, to avoid potential
security vulnerabilities, the installer program no longer includes a JRE.
Instead, the installer program uses the JRE in your environment to allow for
the most secure version of a JRE to be used.
Notes:
- This change does not affect the JVM requirements for the driver. For the latest
driver requirements, refer to the Product Compatibility Guide:
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf
- The installer program cannot remove the already installed JRE files from the
install directory automatically. Remove them manually.
- To install the 32-bit drivers on 64-bit Windows platforms and start the SQL
engine service, the installer requires the 32-bit version of Java SE 11 or
higher installed on your machine and defined on your path.
* The installer program has been updated to no longer install common components
for drivers that do not use them. As a result, the installer program no longer
installs the following common components for the GitHub driver:
- OpenSSL library files, such as ivopenssl30.dll, ddopenssl30.dll, fips.dll, and
openssl.cnf.
- Curl library files, such as ivcurl28.dll and ddcurl28.dll.
If the files are not used by any other DataDirect driver on your machine, you
can safely remove them from existing product directories.
* The Server Name (ServerName) connection option has been renamed Host Name
(HostName). To support existing configurations, the ServerName attribute will
continue to be supported as an alias for the Host Name option.
* The default value of the Authentication Method connection option has
been changed to 34 (BearerToken).
* The default value of the SQL Engine Mode connection option has been
changed to 1 (Server).
Release 8.0.0 Features
The Progress DataDirect for ODBC for GitHub driver supports SQL read-only
access for ODBC applications to GitHub. The driver provides access to
data in GitHub Enterprise and GitHub Cloud, which can be pulled into a data
visualization tool to get important insights into engineering operations.
In addition, the driver employs a SQL engine component that provides support
to SQL constructs to provide the most comprehensive SQL support and ODBC
standard-based connectivity to BI and ETL tools. To support SQL access to
GitHub services, the driver creates a relational map of the GitHub data model
and translates SQL statements to GitHub REST API requests.
Features:
* Supports SQL read-only access to GitHub Enterprise and Cloud.
* Supports all ODBC Core and Level 1 functions and some Level 1 and
Level 2 features.
* Supports GitHub data types through data type inference.
* Supports OAuth 2.0 authentication.
* Supports Basic authentication.
* Supports the handling of large result sets with paging and the
Fetch Size (FetchSize) connection option.
* Includes a redesigned ODBC Setup dialog, the DataDirect ODBC Driver
Configuration Manager, for quick configuration and testing of your driver.
This Configuration Manager allows you to:
- Configure data sources
- Generate and edit connection strings
- Test connect data sources and connection strings
- Execute SQL commands for testing
- Fetch OAuth tokens and configure OAuth
- Access connection property descriptions and the full product
documentation
DataDirect ODBC Driver Configuration Manager
The driver includes an enhanced setup dialog, the DataDirect ODBC
Driver Configuration Manager, that allows you to generate and test connection
URLs that you can use with your application. You can launch the Configuration
Manager by opening the ODBC Administrator from the Progress DataDirect
program group and creating or configuring a data source for the driver.
For more information, refer to the user's guide for your driver.
Notes, Known Problems, and Restrictions
The following are notes, known problems, and restrictions for the
8.0 release of the driver:
Specifying values for the same connection option multiple times
---------------------------------------------------------------
The driver does not support specifying values for the same connection
option multiple times in a connection string or DSN. If a value is
specified using the same attribute multiple times or using both
long and short attributes, the connection may fail or the driver may
not behave as intended.
Bearer token authentication
---------------------------
To configure the driver to use bearer token authentication:
* Set the Server Name (ServerName) option to the base URL
of the GitHub instance to which you want to issue requests.
For example, https://github.<enterprise>.com.
* Set the Security Token option to specify the personal access
token assigned to you.
Note: The Security Token option is not required to be stored
in the connection string. It can also be passed separately
by the application.
The following examples show the connection information required
to establish a session using bearer token authentication.
Connection string:
DRIVER=DataDirect 8.0 GitHub;ServerName=github.<enterprise>.com;
SecurityToken=12a3=bCD/EfGh4Ijk+Lgd8g-44tk3c527831;
odbc.ini:
[GitHub]
Driver=ODBCHOME/lib/ivgithub28.so
Description=DataDirect 8.0 GitHub
...
ServerName=github.<enterprise>.com
...
SecurityToken=12a3=bCD/EfGh4Ijk+Lgd8g-44tk3c527831;
...
No Configuration Manager Support for File DSNs
----------------------------------------------
The Configuration Manager does not currently support creating File
DSNs. If you attempt to add a File DSN, the Configuration Manager
creates a User DSN instead.
Configuration Manager not Supported on Internet Explorer
--------------------------------------------------------
The Configuration Manager is not supported on the Internet Explorer
browser. Also, the OAuth functionality may not work as expected for
the requests coming from Internet Explorer because GitHub has
stopped supporting them.
SQL Engine Direct Mode on Windows 32-bit Operating Systems
----------------------------------------------------------
On Windows 32-bit operating systems, the SQL engine does not
support direct mode (SQLEngineMode=2).
Configuration Manager Navigation Tabs
-------------------------------------
When using the configuration manager, if the web browser window
size is decreased or the system resolution is low, the navigation
tabs may expand into the Help section and become inaccessible.
To work around this issue, either maximize the web browser window
or zoom out the browser view until the tabs become accessible.
OAuth Connection Fails in Direct Mode
-------------------------------------
In configuration manager, when Authentication Method is set to
24-OAuth2 and SQL Engine Mode is set to 2-Direct, the driver fails
to connect to GitHub. However, it connects successfully when SQL Engine
Mode is set to 0-Auto and SQL engine service is running. Also, it
connects successfully when the same settings are used outside the
configuration manager.
Logon Dialog Box Appears for Each Query
---------------------------------------
When attempting to execute queries, the configuration manager displays
the logon dialog box for each query. The logon dialog box contains
the credentials entered at connection. Click OK to proceed.
Optional Fields in the Logon Dialog Box
----------------------------------------
When attempting to authenticate to a GitHub service using OAuth
authentication through a third-party application like Tableau, the
configuration manager keeps displaying the logon dialog box until
you fill up all fields in it, including the optional fields.
Connecting to a GitHub Cloud Instance without Specifying the
Password
-------------------------------------------------------------
If you attempt to connect to a GitHub cloud instance without specifying
the password, the driver establishes the connection and allows you to
query public repositories and objects. However, it returns an "Invalid
Credentials" error if you attempt to query the private repositories or
objects.
Two-factor Authentication
-------------------------
The driver does not support two-factor authentication.
Child Tables with Mandatory Filters
-----------------------------------
If you execute a query on a child table that has mandatory filters, the driver
returns an error message that reports corresponding parent columns.
Invalid Client Secret in the GitHub Configuration Manager
---------------------------------------------------------
In the GitHub Configuration Manager, if you enter an invalid client secret
value while fetching the OAuth tokens, the driver does not return an error
message.
Aggregates for Date/Time Data Types
-----------------------------------
The MIN and MAX aggregates for the Date/Time data types may return incorrect
values.
Connection issues when specifying ExtendedOptions
-------------------------------------------------
When specifying a value for the Extended Options (ExtendedOptions) option in
the Configuration Manger, the driver currently adds the option and its value to
the Connection String field. However, the ExtendedOptions attribute is not
supported in Connection Strings; therefore, attempting to connect with the
generated connection string or executing a test connect with the configuration
manager will result in the an “Invalid attribute in the connection string: XO”
error.
To work around this issue, manually edit the connection string to remove
"ExtendedOptions=" from the connection string; then, specify the value of
ExtendOptions as semi-colon separated options in the string.
For example:
Driver=<driver_name>;HostName=<host_name>;ExtendedOptions=WorkArounds2=4096,
WorkArounds2=8192;
Becomes:
Driver=<driver_name>;HostName=<host_name>;WorkArounds2=4096;WorkArounds2=8192;
126 Error When Modifying Data Sources on Windows 10
---------------------------------------------------
You may receive a 126 error when adding or configuring a data source stored
on a network location. This might be caused by the settings of the User Account
Control (UAC) security feature on Windows 10. To work around this issue:
Important: Implementing this fix disables security safeguards that are designed
to protect your machine. Before starting, refer to the following Microsoft
documentation for potential risks associated with disabling the UAC feature:
http://windows.microsoft.com/en-us/
windows/what-are-user-account-control-settings
1. From the Start menu, type regedit in the search field; then, select regedit
from the results list. The Registry Editor window opens.
2. Navigate to the following registry subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
3. Right click on the subkey; then, select New > DWORD Value.
4. Rename the new value EnableLinkedConnections.
5. Right-click EnableLinkedConnections, and then click Modify. The Edit DWORD
Value window opens.
6. In the Value data field, type 1. Click OK.
7. Close the Registry Editor; then, restart your computer.
Driver WorkAround Options
Progress DataDirect has included non-standard connection options (workarounds)
for the driver that enable you to take full advantage of packaged ODBC-enabled
applications requiring non-standard or extended behavior. Refer to the chapter
"WorkAround options" in THE PROGRESS DATADIRECT FOR ODBC DRIVERS REFERENCE for a
description of these options.
Documentation
PROGRESS DATADIRECT FOR ODBC FOR GITHUB DOCUMENTATION SET
---------------------------------------------------------
The driver documentation set is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-github
You can access the online help system directly in either of the following ways.
* Via the HTML redirect in the installation Help directory
* By selecting Help from the information menu (? button) in the Configuration
Manager
Installed Files for the 32-bit Driver
This file list assumes a full installation of the driver and
documentation.
The installer copies the following file to the Windows system
directory:
ivtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
For 32-bit drivers on 64-bit machines:
C:\Program Files (x86)\Progress\DataDirect\ODBC\:
For all other installations:
C:\Program Files\Progress\DataDirect\ODBC\:
\<install_dir>\:
----------------
license.txt Progress DataDirect license agreement
\drivers\:
----------
ivgithub28.dll DataDirect GitHub driver
ivgithub28r.dll DataDirect GitHub driver resource file
ivicu.dll Unicode conversion tables
ivODBC.LIC DataDirect License File
ivtrc28.dll DataDirect trace library
qesqlext.h Header file for DataDirect-specific ODBC
Definitions
\FIXES\:
--------
fixes8.0.txt List of fixes since last release
\help\:
-------
*.html HTML redirects to online connector help systems
and documentation resources
\install\:
---------
*.* Files associated with the installer program
\java\lib\:
-----------
github.jar Java components for the driver
\jre\:
------
*.* Files associated with the installer program
\NOTICES\:
----------
ODBC for GitHub
v8.0 notices.txt Third-party vendor license agreements
\READMES\:
----------
ODBC for GitHub
v8.0 readme.txt This file
\samples\bulk\:
---------------
bulk.c Bulk example source
bulk.exe Bulk application
bulk.mak Bulk example make file
bulk.sln Bulk example solution file
bulk.vcproj Bulk example project file
ddlogging.properties Log configuration file for
the GitHub driver
\samples\bulkstrm\:
------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulk.rc Bulk streaming example resource file
bulkstreaming.sln Bulk streaming example solution file
bulkstreaming.vcproj Bulk streaming example project file
bulkstrm.exe Bulk streaming example application
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
GitHub driver
msgprintf.hpp Bulk streaming example header file
ProgressDataDirect.bmp
ProgressDataDirect.ico
winmain.cpp Bulk streaming example source file
\samples\example\:
------------------
example.c Example source
Example.exe Example application
example.h Example header
Example.mak Example make file
Example.sln Example solution file
Example.vcproj Example project file
\samples\translat:
-----------------
LIBMAIN.C
README.TRN Translation Library example description
TRANSLAT.C Translation Library example source file
WINNT.MAK Translation Library example make file
\tools\:
-------
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNConverterSil.exe Data Source Converter utility
githubserver32.exe The GitHub driver SQL Server Engine
XMLP.exe A GUI demo tool that persists a result set to
an XML data file
\tools\Power BI:
----------------
DataDirectGitHub.pqx GitHub Power BI connector file
install.bat Batch file to install Power BI connectors
\tools\Tableau\:
----------------
DataDirect GitHub.tdc Tableau data source file
\uninstall\:
------------
*.* Files used to uninstall the product
Installed Files for the 64-bit Driver
This file list assumes a full installation of the driver and
documentation.
The installer copies the following file to the Windows system
directory:
ddtrc28.dll DataDirect trace library
The installer copies the following files and subdirectories to the
product installation directory, by default:
C:\Program Files\Progress\DataDirect\ODBC\:
\<install_dir>\:
----------------
license.txt Progress DataDirect license agreement
\drivers\:
----------
ddgithub28.dll DataDirect GitHub driver
ddgithub28r.dll DataDirect GitHub driver resource file
ddicu.dll Unicode conversion tables
DDODBC.LIC DataDirect License File
ddtrc28.dll DataDirect trace library
qesqlext.h Header file for DataDirect-specific ODBC
Definitions
\FIXES\:
--------
fixes8.0.txt List of fixes since last release
\help\:
-------
*.html HTML redirects to online connector help systems
and documentation resources
\install\:
---------
*.* Files associated with the installer program
\java\lib\:
-----------
github.jar Java components for the driver
\jre\:
------
*.* Files associated with the installer program
\NOTICES\:
----------
ODBC for GitHub
v8.0 notices.txt Third-party vendor license agreements
\READMES\:
----------
ODBC for GitHub
v8.0 readme.txt This file
\samples\bulk\:
---------------
bulk.c Bulk example source
bulk.exe Bulk application
bulk.mak Bulk example make file
bulk.sln Bulk example solution file
bulk.vcproj Bulk example project file
ddlogging.properties Log configuration file for
the GitHub driver
\samples\bulkstrm\:
------------------
bulk.cpp Bulk streaming example source
bulk.hpp Bulk streaming example header
bulk.rc Bulk streaming example resource file
bulkstreaming.sln Bulk streaming example solution file
bulkstreaming.vcproj Bulk streaming example project file
bulkstrm.exe Bulk streaming example application
bulkstrm.txt Bulk streaming description
ddlogging.properties Log configuration file for the
GitHub driver
msgprintf.hpp Bulk streaming example header file
ProgressDataDirect.bmp
ProgressDataDirect.ico
winmain.cpp Bulk streaming example source file
\samples\example\:
------------------
example.c Example source
Example.exe Example application
example.h Example header
Example.mak Example make file
Example.sln Example solution file
Example.vcproj Example project file
\samples\translat:
-----------------
LIBMAIN.C
README.TRN Translation Library example description
TRANSLAT.C Translation Library example source file
WINNT.MAK Translation Library example make file
\tools\:
-------
ddextwin.exe License Extender utility
ddprocinfo.exe Processor Information utility
DSNConverterSil.exe Data Source Converter utility
githubserver64.exe The GitHub driver SQL Server Engine
XMLP.exe A GUI demo tool that persists a result set to
an XML data file
\tools\Power BI:
----------------
DataDirectGitHub.pqx GitHub Power BI connector file
install.bat Batch file to install Power BI connectors
\tools\Tableau\:
----------------
DataDirect GitHub.tdc Tableau data source file
\uninstall\:
------------
*.* Files used to uninstall the product
~~~~~~~~~~~~~~~~~~
February 2026
End of README.TXT