README
     Progress (R) DataDirect (R)
	 
     Progress(R) DataDirect(R) for ODBC for MongoDB(TM) Driver

     UNIX and Linux Platforms (32- and 64-bit)
     Release 8.0.1
     November 15, 2017


***********************************************************************
Copyright (C) 1990-2017 Progress Software Corporation and/or its 
subsidiaries or affiliates. All Rights Reserved. 
***********************************************************************

This README file contains information for Progress(R) DataDirect(R)  
for ODBC for MongoDB(TM) Driver. 

This README file contains information not included in the PROGRESS
DATADIRECT(R) FOR ODBC FOR MONGODB DRIVER USER'S GUIDE AND REFERENCE.

CONTENTS

Driver Requirements
Installation Directory
Changes Since 8.0.1 GA 
Changes For 8.0.1 GA 
Release 8.0.0 Features 
The Progress DataDirect for ODBC for MongoDB Driver
Required Operating System Patches
Configuring Data Sources
Driver WorkAround Options
Notes, Known Problems, and Restrictions
Documentation
Installed Files for 32-bit Drivers
Installed Files for 64-bit Drivers
Documentation Third-party Acknowledgements 


    Driver Requirements

The driver requires a Java Virtual Machine (JVM): Java SE 6 or higher. Also,
you must set the library path environment variable of your operating system
to the directory containing your JVM's libjvm.so [sl | a] file and that
directory's parent directory. 

For AIX users: Before you can use the driver, you must set the LIBPATH 
environment variable to include the paths containing the libjvm.so library 
and the libnio.so library, which are installed in a subdirectory of your 
Java Development Kit (JDK). For example, you would add the following paths
for Java 6 installed in the /usr directory:

:/usr/java6/jre/lib/ppc/classic:/usr/java6/jre/lib/ppc

In this example, /usr/java6/jre/lib/ppc/classic is the location of libjvm.so,
while /usr/java6/jre/lib/ppc is the location of libnio.so.


    Installation Directory

* The default installation directory for the 32-bit driver is:

  /opt/Progress/DataDirect/ODBC_80

* The default installation directory for the 64-bit driver is:

  /opt/Progress/DataDirect/ODBC_80_64bit

  
    Changes Since 8.0.1 GA   
  
Certifications
--------------
* Certified with Red Hat Enterprise 7.3 (driver version 
  08.01.0156 (B0251, U0167)
* Certified with MongoDB 3.4 (driver version 08.01.0156 
  (B0251, U0167, J000272))
* Certified with Debian Linux 7.11, 8.5 (driver version 08.01.0115 
  (B0167, U0120))
* Certified with Ubuntu Linux 14.04, 16.04 (driver version 08.01.0115 
  (B0167, U0120))
* Certified with MongoDB 3.2 (driver version 08.01.0102  (B0131, U0094, 
  J000198))
   
Refer to the fixes.txt file in the product installation directory for a list of
changes by build number. 

  
    Changes For 8.0.1 GA

New Operating System Support
---------------------------- 	
* Certified with Red Hat Enterprise 7.1 
* Certified with CentOS Linux 7.1  
* Certified with Oracle Linux 7.1  
* Certified with SUSE Enterprise Server 12  

Name Conflict Resolution
------------------------
The driver has been enhanced to resolve naming conflicts that can occur when
exposing native objects using unquoted, uppercase identifiers (the default
behavior). To avoid conflicts, the driver appends an underscore separator 
and integer (for example, _1) to identifiers that differ only by case. 

DefaultVarcharSize, MaxVarcharSize, and MinVarcharSize Config Options  
---------------------------------------------------------------------
The DefaultVarcharSize config option has been enhanced to generate dynamic 
default lengths for VARCHAR columns when specifying a multiplier value (for
example, 2x) for the option. When specifying a multiplier value, the default
length for a VARCHAR column is determined by multiplying the value specified
by the size of the largest value detected in that column. This results in 
a default length that is proportionate to the size of the data within 
the column, which can improve the memory efficiency within the driver and 
application. The default value for this option has been updated to 1.5x.

In addition, you can further define the default length for VARCHAR columns by 
tuning the new MaxVarcharSize and MinVarcharSize config options. These options 
allow you to specify maximum and minimum size limits for the default length 
generated by the DefaultVarcharSize config option. When tuned for your data,
MaxVarcharSize and MinVarcharSize can provide additional memory efficiency 
and avoid undesired truncation of VARCHAR values.

KeywordConflictSuffix Config Option
-----------------------------------
The new KeywordConflictSuffix config option allows you to specify the suffix 
that is appended to object and field names that conflict with SQL engine 
keywords.

MongoDB Aggregation Framework
-----------------------------
The driver uses the MongoDB aggregation framework to improve performance in the
execution of SQL queries using LIMIT, ORDER BY, or TOP clauses.

New SQL Extensions
------------------
The RELOAD MAP and REFRESH MAP commands have been added to the driver.

* RELOAD MAP reloads the schema definition and associated files. RELOAD MAP
  updates your relational view of native data while the driver is connected to
  the data store. RELOAD MAP does not discover changes made to the native 
  data store. 

* REFRESH MAP discovers native objects that have been added to the native data
  store since connection or since the last refresh. REFRESH MAP incorporates
  newly discovered objects into your relational view of native data. It also 
  incorporates any configuration changes made to your relational view by 
  reloading the schema definition and associated files. REFRESH MAP is an 
  expensive query since it involves the discovery of native data.  
  
Dynamic Fetch Enhancement
-------------------------
The driver has been enhanced to improve the handling of large result sets and
reduce the likelihood of out-of-memory errors through the modification of the
Fetch Size connection option and the introduction of the Result Memory Size
connection option. 
  
For more information about these features, refer to THE PROGRESS DATADIRECT FOR
ODBC FOR MONGODB DRIVER USER'S GUIDE AND REFERENCE.  
  
  
    Release 8.0.0 Features 
   
Certifications
--------------
* Certified with MongoDB 3.0 

Automatic Schema Definition Creation
------------------------------------
When first connecting to a MongoDB server, the driver automatically creates a
normalized schema of the data and generates a Schema Definition for housing and
sharing the normalized schema.

Full Normalization of Native Objects 
------------------------------------
Native MongoDB data is fully normalized during the normalization process, 
regardless of the depth of nested arrays, documents, and objects.

MongoDB Aggregation Framework
-----------------------------
The driver uses the MongoDB aggregation framework to improve performance in 
the execution of SQL queries using aggregates, GROUP BY clauses, or HAVING clauses.

Schema Tool Enhancements 
------------------------
* The new Restart Wizard feature allows you to reset the relational view of 
  your data from the Table Wizard menu.
* The new Update Schema feature allows you to map all new native objects to 
  your schema definition with a single click.
* Support for selecting multiple objects in the Table Wizard for improved 
  object management when customizing your schema. 

Min Long Varchar Connection Option 
----------------------------------
The new Min Long Varchar Size connection option allows you to fetch
SQL_LONGVARCHAR columns whose size is smaller than the minimum
imposed by some third-party applications. 

Varchar Threshold Connection Option 
-----------------------------------
The new Varchar Threshold connection option allows you to fetch columns
that would otherwise exceed the upper limit of the SQL_VARCHAR type for some
third-party applications. 

SQL Engine Mode Auto Setting
---------------------------- 
The SQL Engine Mode connection option now supports Auto mode. When this setting 
is enabled, the driver automatically determines whether the SQL engine runs in
server or direct mode based on availability. 

UTF-8 Support in the odbc.ini and odbcinst.ini Files
----------------------------------------------------
The driver and Driver Manager have been enhanced to support UTF-8 encoding in 
the odbc.ini and odbcinst.ini files.

For more information about these features, refer to THE PROGRESS DATADIRECT FOR
ODBC FOR MONGODB DRIVER USER'S GUIDE AND REFERENCE.

  
   The Progress DataDirect for ODBC for MongoDB Driver 

The Progress DataDirect for ODBC for MongoDB Driver supports standard SQL query 
language to select data from MongoDB databases. In addition, some insert, 
update, and delete capabilities are supported. The driver translates the 
SQL statements provided by an application into native MongoDB-BSON statements,
enabling you to leverage your knowledge of SQL. The driver also includes
the DataDirect Schema Tool, which guides you through the process of mapping 
the MongoDB dynamic schema data model to a customized relational data model.  

Features:
--------
	
* The driver has been certified against the following MongoDB databases:
  * MongoDB version 3.0 
  * MongoDB version 2.2, 2.4, 2.6

* The driver supports all ODBC Core functions. 

* The driver supports the core SQL 92 grammar.

* The driver supports advanced security features, including SSL data 
  encryption.

* The driver supports the following data types:
  - Array		maps to SQL_LONGVARCHAR
  - Bigint		maps to SQL_BIGINT
  - BinData		maps to SQL_VARBINARY
  - Boolean		maps to SQL_BIT
  - Date		maps to SQL_TIMESTAMP
  - Double		maps to SQL_DOUBLE
  - Integer		maps to SQL_INTEGER
  - Object		maps to SQL_WLONGVARCHAR
  - ObjectID	        maps to SQL_WVARCHAR
  - String		maps to SQL_WCHAR, SQL_WVARCHAR, and SQL_WLONGVARCHAR
  
* The DataDirect Schema Tool:
  - Enables you to flatten, normalize, or customize your view of 
    MongoDB data.
  - Allows you to decide which MongoDB objects are extracted into 
    relational views.  
  - Provides information and statistics about your data. 
  - Exposes tabular relationships among your MongoDB collections.
  - Enables you to define your column data types.
  - Allows schema definitions to be shared across servers.
  - Supports advanced security features, including SSL data encryption. 
 
 
    Required Operating System Patches

For HP-UX 11 aCC Users Only
---------------------------
The ODBC drivers for HP-UX 11 aCC are supported on HP-UX 11.0
when running with HP-UX applications built using the HP aCC 
compiler version 3.05 or higher.

The ODBC drivers require certain runtime library patches. HP-UX 
patches are publicly available from the HP Web site (www.hp.com). The 
required patch is:

PHSS_14577

HP updates the patch database regularly; therefore, the patch 
numbers in this file may be superseded by newer versions. If you 
search for any of the specified patches on an HP site and receive 
a message that a patch has been superseded, download and install 
the replacement patch.
 
 
      Configuring Data Sources

Data sources are stored in the system information file (typically, 
odbc.ini). For details on configuring this file, see the PROGRESS DATADIRECT
FOR ODBC FOR MONGODB DRIVER USER'S GUIDE AND REFERENCE.
 
 
      Driver WorkAround Options

Progress DataDirect has included non-standard connection options 
(workarounds) for the drivers 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
FOR MONGODB DRIVER USER'S GUIDE AND REFERENCE for a description of these 
options.
 
 
	Notes, Known Problems, and Restrictions 
  
Out-of-Memory Errors
--------------------
When processing large sets of data, out-of-memory errors can occur when the size
of an intermediate result exceeds the available memory allocated to the JVM. If
you are encountering these errors, you can tune Fetch Size or Result Memory 
Size to fit your environment.

* Reduce Fetch Size to reduce demands on the driver's internal memory. By
  lowering the maximum number of rows as specified by Fetch Size, you lower the
  number of rows the driver is required to process before returning data to the
  application. Thus, you reduce demands on the driver's internal memory, and, 
  in turn, decrease the likelihood of out-of-memory errors.
  
* To tune Result Memory Size, decrease the value specified until results are 
  successfully returned. Intermediate results larger than the specified setting
  will be written to disk as opposed to held in memory. When configured 
  correctly, this avoids memory limitations by not relying on memory to process
  larger intermediate results. Be aware that while writing to disk reduces the 
  risk of out-of-memory errors, it also negatively impacts performance. For 
  optimal performance, decrease this value only to a size necessary to avoid 
  errors. 
  
  By default, Result Memory Size is set to -1, which sets the maximum 
  size of intermediate results held in memory to a percentage of the max Java
  heap size. If you received errors using the default configuration, use the 
  max Java heap size divided by 4 as a starting point when tuning this option.    
	
Performance Issues When Executing Queries
-----------------------------------------
The 8.0.x driver pushes down SQL queries to MongoDB whenever possible. Queries 
that cannot be pushed down to MongoDB in the 8.0.x driver may be slower than 
comparable queries made with previous versions of the driver because data may 
be paged to disk while completing an operation. If you experience slow 
performance, please contact Technical Support: 
https://www.progress.com/support-and-services. Our team will quickly address 
any performance issues you may encounter.

In-Memory Tables
----------------
The driver no longer supports in-memory, or local, tables. As a result, alters,
creates, and drops are no longer supported. 	

SQL Engine Upgrade
------------------
The driver's SQL engine was upgraded for Release 8.0. Therefore, there 
are some differences in how the 8.0 driver handles SQL queries compared to 
previous versions of the driver. For more information, visit:
https://www.progress.com/products/datadirect-connect/data-connectivity-features
/content/progress-datadirect-sql-engine-upgrade 	

Normalization Depth Option
--------------------------
The Normalization Depth option is no longer available in the Schema Tool 
because native MongoDB data is now fully normalized, regardless of depth, 
during the normalization process.

Support for 7.1.x Schema Definitions
------------------------------------
The 8.0.x version of the driver and Schema Tool do not support schema 
definitions created with previous versions of the product. Therefore, you
should reproduce your  7.1.x schema definitions with the 8.0.x driver or 
Schema Tool. 
	
Primary Keys in a Sharded Environment
-------------------------------------	
_id is assumed to be the primary key and row identifier for all tables
exposed via the driver. This assumption is typically valid; however, if
you are working with a sharded MongoDB collection, _id is not guaranteed
to be unique unless _id has been defined as the shard key for that 
collection. If the _id is not unique, write and join operations could
produce unpredictable and undesired results. 
  
To avoid undesired results, verify that the values of _id are unique 
before disabling the ReadOnly connection option. If needed, you can also 
designate the shard key as your primary key using the DataDirect
Schema Tool. For more information on designating the primary key, refer
to the "Using the Driver" chapter of the USER'S GUIDE AND REFERENCE.   
	
VARCHAR Truncation
------------------
For columns mapped to VARCHAR, the driver truncates values that exceed the
column size defined for the column when constructing the relational map of your
data. Refer to "About Column Information and Statistics" in the USER'S
GUIDE AND REFERENCE for details.

During the initial discovery and normalization process, you can use the
defaultVarcharSize configuration option to specify the default length of fields
that are discovered and mapped as Varchar by the driver. Refer to "Starting
the Schema Tool" in the USER'S GUIDE AND REFERENCE for details.

After the initial discovery and normalization process, you can define the
column size of individual columns from the main display of the Schema Tool.
Refer to "Defining Columns" in the USER'S GUIDE AND REFERENCE for details.

You can find the column size defined for a column either by selecting a table
from the main display of the Schema Tool or by calling or by executing the 
SQLColumns function.

VARBINARY Truncation
--------------------
For columns mapped to Varbinary, the driver truncates values that exceed the
column size defined for the column when constructing the relational map of your
data. Refer to "About Column Information and Statistics" in the 
USER'S GUIDE AND REFERENCE for details.

After the initial discovery and normalization process, you can define the
column size of individual columns from the main display of the Schema Tool.
Refer to "Defining Columns" in the USER'S GUIDE AND REFERENCE for details.

You can find the column size defined for a column either by selecting a table
from the main display of the Schema Tool or by executing the SQLColumns 
function.	
	
Write Operations When Connected to a Replica Set
------------------------------------------------
When connected to a replica set, you can execute Select, Insert, and Delete
against the primary node. However, you can only execute Select against
secondary members (follower servers).

Mapped Columns with Numeric Names
---------------------------------
When accessing data from a mapped column with a numeric name, you must 
enclose the column name in double quotes in the SQL statement. For example,
to select data from a column named 3, you submit the following statement:

SELECT "3" FROM <table>

Although numeric column names can be created a number of ways, they are 
typically the result of normalizing a collection that contains array fields. 

system.indexes Collection and Tables
------------------------------------
The driver hides the system.indexes collection and tables containing the
"$" character are hidden to prevent naming conflicts. 

oplog.rs System Table
---------------------  
The driver hides the oplog.rs system table.
  
ODBC Development on UNIX and Linux Platforms
--------------------------------------------
All of the Release 7.1 Core Components (header files, etc.) needed for 
development of ODBC applications on UNIX and Linux are installed into 
the /include directory created by the product installer.

Please read the notices.txt file in the installation directory for 
licensing information regarding the ODBC Core Components. Contact your 
Progress DataDirect representative if you have any questions.

Developers using programming languages other than C++:
The DataDirect ODBC Driver Manager is a C++ shared library. The ODBC 
Driver Manager can be used with any language that supports loading a 
C++ shared library; however, if you are using a programming language 
other than C++, you must take additional steps to ensure that the C++ 
libraries are initialized properly when loaded. If you are not using 
C++, consult your compiler documentation for instructions on using C++ 
shared libraries with your application.
  
LANG Environment Setting on UNIX and Linux Platforms
----------------------------------------------------
A default installation of the product on UNIX and Linux assumes that 
the value of the LANG environment setting is en_US. If your locale is 
not set to en_US, the drivers may not return error messages properly. 
In this case, you must create a symbolic link in the 
<Install_Dir>/locale directory that has the same value as the LANG 
environment setting. This link must point to the 
<Install_Dir>/locale/en_US directory.
 
SQLColAttribute(s)
------------------
The column attributes 1001 and 1002, which were assigned as DataDirect- 
specific attributes, were inadvertently used as system attributes by
the Microsoft 3.0 ODBC implementation. Applications using those 
attributes must now use 1901 and 1902, respectively.
 
SQLDriverConnect
----------------
SQLDriverConnect using options other than SQL_DRIVER_NOPROMPT is 
supported only on systems that include the Motif libraries 
libivmback.so or libddmback.so and vscnctdlg.so.
 
SQL_C_NUMERIC
-------------
Because of inconsistencies in the ODBC specification, users attempting 
to use SQL_C_NUMERIC parameters must set the precision and scale values 
of the corresponding structure and the descriptor fields in the 
Application Parameter Descriptor.

For AIX Users
------------------------------
Some IBM AIX C compilers, such as xlc 3.1.4, do not support the use 
of C++ build binaries. C developers on AIX should consult their 
compiler documentation and verify that their AIX C compiler supports 
the use of C++ shared libraries or the application could be unstable.
 
 
     Documentation	 	 

THE PROGRESS DATADIRECT FOR ODBC FOR MONGODB DRIVER USER'S GUIDE AND REFERENCE
------------------------------------------------------------------------------
This guide is provided in PDF and HTML versions. 

The PDF version is available on the Progress DataDirect Web site, which you can
view using Adobe Reader. 

NOTE: To download Adobe Reader, visit the Adobe Web site at 
http://www.adobe.com.

The HTML version of the book is installed in the MongoDBHelp subdirectory of
your product installation directory. You can access the help by opening the 
index.html file.

A separate Schema Tool help system is packaged with the driver. This help
system is installed in the SchemaToolHelp subdirectory of your product 
installation directory. The content of the Schema Tool help is also 
included in the User's Guide and Reference. 


     Installed Files for the 32-bit Driver
	 
This file list assumes a full installation of all 32-bit drivers and 
documentation. 

The installer copies the following files and subdirectories to the 
product installation directory, by default:

/opt/Progress/DataDirect/ODBC_80:

odbc.csh              Setup script for C shell
odbc.ini              Sample odbc.ini file
odbcinst.ini          Sample odbcinst.ini file
odbc.sh               Setup script for Bourne shell
IVODBC.LIC            DataDirect license file
fixes.txt             List of fixes since last release

/bin:
ivtestlib            Test application to check that required libraries
                     are present and loadable
/help: 
mongo_connect.txt    Help text for the MongoDB driver 
                     SQLDriverConnect dialog 
/help/MongoDBHelp:
index.html           HTML help system entry file
*.*                  Support folders for the HTML help system

/help/SchemaToolHelp:
index.html           HTML help system entry file
/SchemaToolHelp/*.*  Support folders for the HTML help system

/include:
odbcinst.h            Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h

/java/lib:
mongodb.jar         Java components for the MongoDB driver


/lib:
The following library files all have the extension .so, except when 
installed on HP-UX PA-RISC, in which case the extension is .sl.

ivmongo28.so          MongoDB driver  
ivtrc28.so            Progress DataDirect trace library
libivcurl28.so        Library used for HTTP connections [.a on AIX]
libivicu28.so         Unicode conversion tables  [.a on AIX]
libivmback.so         SQLDriverConnect Motif library 
libivssl28.so	  SSL support file 
libodbc.so            ODBC Driver Manager [.a on AIX]
libodbcinst.so        ODBC Installer [.a on AIX]
odbc.so               ODBC Driver Manager (dynamically loadable) 
                      [AIX only]
odbccurs.so           ODBC Cursor library 
odbcinst.so           ODBC Installer (dynamically loadable) 
                      [AIX only]
vscnctdlg.so          ODBC library for Motif operations


/locale/en_US/LC_MESSAGES:
ivmbackw.mo           Motif library message file
ivmbackw.po           Motif library message source
ivmongo28.mo          MongoDB driver message file
ivmongo28.po          MongoDB driver message file source
odbc.mo               ODBC Driver Manager message file
odbc.po               ODBC Driver Manager message source


/NOTICES:
ODBC for MongoDB v8.0 notices.txt   Third-party vendor license agreements	


/READMES:
ODBC for MongoDB v8.0 readme.txt	This file

/samples:
/bulk/bulk                  Bulk application
/bulk/bulk.c                Bulk example source
/bulk/bulk.mak              Bulk example make file
/bulk/bulk.txt              Bulk example description
/bulk/ddlogging.properties  Log configuration file for the MongoDB driver

/bulkstrm/bulk.cpp          Bulk streaming example source
/bulkstrm/bulk.hpp          Bulk streaming example header
/bulkstrm/bulkstrm          Bulk streaming example application
/bulkstrm/bulkstrm.txt      Bulk streaming example description
/bulkstrm/main.cpp          Bulk streaming example source
/bulkstrm/msgprintf.hpp     Bulk streaming example header
/bulkstrm/streambulk.mak    Bulk streaming example make file
/bulkstrm/ddlogging.properties    Log configuration file for the 
                                  MongoDB driver

/example/example                 Example application
/example/example.c               Example source
/example/example.h               Example header
/example/example.mak             Example make file
/example/example.txt             Example description
/example/ddlogging.properties    Log configuration file for the 
                                 MongoDB driver

/tools:
ddextu                    License Extender utility
ddprocinfo                Processor Information utility
schematool.jar	          The Progress DataDirect Schema Tool				  
          
		  
  Installed Files for the 64-bit Driver
	 
This file list assumes a full installation of the 64-bit driver and 
documentation. 

The installer copies the following files and subdirectories to the 
product installation directory, by default:

/opt/Progress/DataDirect/ODBC_80_64bit:


odbc.csh              Setup script for C shell
odbc.ini              Sample odbc.ini file
odbcinst.ini          Sample odbcinst.ini file
odbc.sh               Setup script for Bourne shell
DDODBC.LIC            DataDirect license file
fixes.txt             List of fixes since last release

/bin:
ddtestlib            Test application to check that required libraries
                     are present and loadable

/help: 
mongo_connect.txt    Help text for the MongoDB driver 
                     SQLDriverConnect dialog 
/help/MongoDBHelp:
index.html           HTML help system entry file
*.*                  Support folders for the HTML help system

/help/SchemaToolHelp:
index.html           HTML help system entry file
/SchemaToolHelp/*.*  Support folders for the HTML help system

/include:
odbcinst.h            Include files
qesqlext.h
sql.h
sqlext.h
sqltypes.h
sqlucode.h
sqlunx.h

/java/lib:
mongodb.jar         Java components for the MongoDB driver

/lib:
ddmongo28.so          MongoDB driver  
ddtrc28.so            Progress DataDirect trace library
libddcurl28.so        Library used for HTTP connections [.a on AIX]
libddicu28.so         Unicode conversion tables  [.a on AIX]
libddmback.so         SQLDriverConnect Motif library 
libddssl28.so	      SSL support file [.a on AIX]
libodbc.so            ODBC Driver Manager [.a on AIX]
libodbcinst.so        ODBC Installer [.a on AIX]
odbc.so               ODBC Driver Manager (dynamically loadable) 
                      [AIX only]
odbccurs.so           ODBC Cursor library 
odbcinst.so           ODBC Installer (dynamically loadable) 
                      [AIX only]
vscnctdlg.so          ODBC library for Motif operations


/locale/en_US/LC_MESSAGES:
ddmbackw.mo           Motif library message file
ddmbackw.po           Motif library message source
ddmongo28.mo          MongoDB driver message file
ddmongo28.po          MongoDB driver message file source
odbc.mo               ODBC Driver Manager message file
odbc.po               ODBC Driver Manager message source


/notices:
ODBC for MongoDB v8.0 notices.txt	  Third-party vendor license agreements	


/readmes:
ODBC for MongoDB v8.0 readme.txt	  This file


/samples:
/bulk/bulk                      Bulk application
/bulk/bulk.c                    Bulk example source
/bulk/bulk.mak                  Bulk example make file
/bulk/bulk.txt                  Bulk example description
/bulk/ddlogging.properties      Log configuration file for the 
			        MongoDB driver

/bulkstrm/bulk.cpp        	Bulk streaming example source
/bulkstrm/bulk.hpp        	Bulk streaming example header
/bulkstrm/bulkstrm        	Bulk streaming example application
/bulkstrm/bulkstrm.txt    	Bulk streaming example description
/bulkstrm/main.cpp        	Bulk streaming example source
/bulkstrm/msgprintf.hpp   	Bulk streaming example header
/bulkstrm/streambulk.mak  	Bulk streaming example make file
/bulkstrm/ddlogging.properties  Log configuration file for the 
                                MongoDB driver

/example/ddlogging.properties	Log configuration file for the MongoDB driver
/example/example          	Example application
/example/example.c        	Example source
/example/example.h        	Example header
/example/example.mak      	Example make file
/example/example64.txt    	Example description
/example/ddlogging.properties   Log configuration file for the 
                                MongoDB driver

/tools:
ddextu                    License Extender utility
ddprocinfo                Processor Information utility
schematool.jar		  The Progress DataDirect Schema Tool	
					  
		  		  
		  
    Documentation Third-party Acknowledgements 

One or more products in the Progress DataDirect for ODBC for MongoDB v8.0 
release includes third party components covered by licenses that require that
the following documentation notices be provided.  If changes in third party 
components occurred for the current release of the Product, the following 
Third Party Acknowledgements may contain notice updates to any earlier 
versions provided in documentation or README file. 
 
Progress DataDirect for ODBC for MongoDB v8.0 incorporates ICU v4.2.1 from
International Business Machines Corporation.  Such technology is subject to 
the following terms and conditions:  ICU License - ICU 1.8.1 and later ICU
License - ICU 1.8.1 and later COPYRIGHT AND PERMISSION NOTICE. 
Copyright (c) 1995-2010 International Business Machines Corporation and 
others. All rights reserved. Permission is hereby granted, free of charge,
to any person obtaining a copy of this software and associated documentation 
files (the "Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish, distribute,
and/or sell copies of the Software, and to permit persons to whom the Software
is furnished to do so, provided that the above copyright notice(s) and this
permission notice appear in all copies of the Software and that both the above
copyright notice(s) and this permission notice appear in supporting 
documentation. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF 
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD
PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR HOLDERS INCLUDED IN 
THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR CONSEQUENTIAL 
DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS,
WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. Except 
as contained in this notice, the name of a copyright holder shall not be used
in advertising or otherwise to promote the sale, use or other dealings in this
Software without prior written authorization of the copyright holder.  All
trademarks and registered trademarks mentioned herein are the property of 
their respective owners.

Progress DataDirect for ODBC for MongoDB v8.0 incorporates HyperSQL database 
v2.3.0 from The HSQL Development Group.  Such technology is subject to the 
following terms and conditions: Copyright (c) 2001-2012, The HSQL Development
Group All rights reserved.
Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met:
Redistributions of source code must retain the above copyright notice, this 
list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this
list of conditions and the following disclaimer in the documentation and/or 
other materials provided with the distribution. 
Neither the name of the HSQL Development Group nor the names of its 
contributors may be used to endorse or promote products derived from this 
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE 
DISCLAIMED. IN NO EVENT SHALL HSQL DEVELOPMENT GROUP, HSQLDB.ORG, OR 
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, 
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, 
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER
IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE 
POSSIBILITY OF SUCH DAMAGE.

Progress DataDirect for ODBC for MongoDB v8.0 incorporates JGoodies Forms 
v1.3.0 from JGoodies Software GmbH.  Such technology is subject to the 
following terms and conditions:  The BSD License for the JGoodies Forms - 
Copyright (c) 2002-2014 JGoodies Software GmbH. All rights reserved.
Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright notice, this
  list of conditions and the following disclaimer. 
* Redistributions in binary form must reproduce the above copyright notice, 
  this list of conditions and the following disclaimer in the documentation 
  and/or other materials provided with the distribution. 
* Neither the name of JGoodies Software GmbH nor the names of its contributors
  may be used to endorse or promote products derived from this software without
  specific prior written permission.  
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" 
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE 
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Progress DataDirect for ODBC for MongoDB v8.0 incorporates OpenSSL toolkit 
v1.0.0_x and OpenSSL toolkit v1.0.2_x from The OpenSSL Project. Such technology
is subject to the following terms and conditions:  
LICENSE ISSUES ============== The OpenSSL toolkit stays under a dual license, 
i.e. both the conditions of the OpenSSL License and the original
SSLeay license apply to the toolkit. See below for the actual license texts.
Actually both licenses are BSD-style Open Source licenses. In case of any 
license issues related to OpenSSL please contact openssl-core@openssl.org.
OpenSSL License --------------- 
Copyright (c) 1998-2011 The OpenSSL Project.  All rights reserved.
Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer. 
2. Redistributions in binary form must reproduce the above copyright notice, 
   this list of conditions and the following disclaimer in the documentation 
   and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
   display the following acknowledgment: "This product includes software 
   developed by the OpenSSL Project for use in the OpenSSL Toolkit.
  (http://www.openssl.org/)"  
4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to 
   endorse or promote products derived from this software without prior written
   permission. For written permission, please contact openssl-core@openssl.org.
5. Products derived from this software may not be called "OpenSSL" nor may 
   "OpenSSL" appear in their names without prior written permission of the
   OpenSSL Project.  
6. Redistributions of any form whatsoever must retain the following 
   acknowledgment: "This product includes software developed by the OpenSSL 
   Project for use in the OpenSSL Toolkit (http://www.openssl.org/)"  
THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO
EVENT SHALL THE OpenSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.  
====================================================================
This product includes cryptographic software written by Eric Young 
(eay@cryptsoft.com).  This product includes software written by Tim Hudson
(tjh@cryptsoft.com).  
Original SSLeay License  ----------------------- Copyright (C) 1995-1998 
Eric Young (eay@cryptsoft.com) All rights reserved.
This package is an SSL implementation written by Eric Young 
(eay@cryptsoft.com). The implementation was written so as to conform with 
Netscapes SSL. This library is free for commercial and non-commercial use as
long as the following conditions are aheared to.  The following conditions 
apply to all code found in this distribution, be it the RC4, RSA, lhash, DES,
etc., code; not just the SSL code.  The SSL documentation included with this
distribution is covered by the same copyright terms except that the holder is
Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such 
any Copyright notices in the code are not to be removed. If this package is 
used in a product, Eric Young should be given attribution as the author of 
the parts of the library used. This can be in the form of a textual message 
at program startup or in documentation (online or textual) provided with the
package. Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the copyright notice, this list 
   of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, 
   this list of conditions and the following disclaimer in the documentation 
   and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must
   display the following acknowledgement: "This product includes cryptographic
   software written by Eric Young (eay@cryptsoft.com)" The word 'cryptographic'
   can be left out if the routines from the library being used are not 
   cryptographic related :-).   
4. If you include any Windows specific code (or a derivative thereof) from the 
   apps directory (application code) you must include an acknowledgement: "This
   product includes software written by Tim Hudson (tjh@cryptsoft.com)"   
THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF 
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO 
EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, 
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT 
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING 
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.   
The licence and distribution terms for any publically available version or 
derivative of this code cannot be changed.  i.e. this code cannot simply be 
copied and put under another distribution licence [including the GNU Public
Licence.] 
Progress DataDirect for ODBC for MongoDB v8.0 incorporates Stax2 API v3.1.1 
from Codehaus.  Such technology is subject to the following terms and 
conditions:  Copyright (c) 2004-2010, Woodstox Project 
(http://woodstox.codehaus.org/) All rights reserved.
Redistribution and use in source and binary forms, with or without 
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this
   list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, 
   this list of conditions and the following disclaimer in the documentation
   and/or other materials provided with the distribution.   
3. Neither the name of the Woodstox XML Processor nor the names of its 
   contributors may be used to endorse or promote products derived from this 
   software without specific prior written permission.  
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE 
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR 
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER 
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 
 
~~~~~~~~~~~~~~
November 15, 2017

End of README.TXT