4 min read

Flex2SQL v10.1 Features

Mertech is pleased to announce the upcoming beta of Mertech's Flex2SQL v10.1 drivers which we plan to release on June .  We plan to release the beta during the week of  June 24th.
Flex2SQL v10.1 is a  minor upgrade from v10.0x drivers released earlier last year. In v10.1, our overarching objective is to make it easier to work with  DataFlex development tools and SQL administration tools.
The foundation for tighter integration between the DataFlex and SQL worlds was laid in the initial release of v10 drivers with the elimination of the table definition files. The .TD files were created to make OPEN calls faster when working with SQL but at a price; any change to the table structure on the database server required deleting the .TD files to get the updated structure. This lead to unnecessary deployment headaches. We improved the efficiency of our OPEN calls so that we now get updated information from the server when the file is opened without affecting performance.
In order to have to co-exist amicably with changes made to table structures, we will need to store (and retrieve)  as much information on the servers as possible, without breaking DataFlex functionality.
Developers interested in participating in the beta please contact Mertech technical support.
The following are the highlights of the new version:
<h5>Store relationship information in the database</h5>
Currently, the relationship information between files is stored in the INT file. With V10.1 drivers, users will be able to recreate all DataFlex relationships directly on the server, and will also be able to read relationship information on the server back into DataFlex.
<h5>Mixed-case table and field names </h5>
Currently we allow all object names to be either all upper case or lower case and the field names follow the convention selected for the table name. In v10.1, users will be able to define their table names and field anyway they prefer.
<h5> Inverse Key data integrity check </h5>
We are introducing a new data checker for diagnosing problems with inverse key field values
<h5> Convert tables types from recnum to RowID tables</h5>
Users will be able to create ROWID tables using VDF Studio as well as convert existing RECNUM tables to ROWID tables using our migration utility.
<h5>Save multiple connection strings in login dialog </h5>
The current login dialog box only allows users to connect to one server. With this enhancement, users will be able to switch between multiple server back ends and save the login information. This is useful in a development environment where developers have to switch between development or training server to and production server.
<li>Saving multiple logins in the login dialog – easier to switch between different servers </li>
<h5>New SQL script for database maintenance </h5>
In addition to scripts for creating or dropping objects, the new scripts will allow analyzing and adjust database after loader executions, adjusting sequences and handling line feed characters in in text files and also scripts for turning on triggers.
<h5> Increase in ESQL performance</h5>
We have improved performance of ESQL code in retrieving data, especially  when using variables to bind values.
<h5> New API ready for low level ESQL calls </h5>
Our current ESQL engine is implemented through the DataFlex ICODE engine using FMAC commands. We have built a completely new driver level  API to allow building object-oriented ESQL classes for working with multiple result sets, simplifying stored procedure and function.
<h5> Tablespace control (PostgreSQL only) </h5>
Allows PostgreSQL users to select the table space where they want to create tables.

Mertech will be releasing the beta of its Flex2SQL v10.1 drivers during the week of  June 24th. Flex2SQL v10.1 is a minor upgrade from the v10.0x drivers released earlier last year. In v10.1, our overarching objective is to make it easier to work with  DataFlex development tools and SQL administration tools. This effort will continue in future releases.


The foundation for tighter integration between the DataFlex and SQL worlds was laid in the initial release of v10 drivers with the elimination of the table definition files. The .TD files were created to make OPEN calls faster when working with SQL but at a price; any change to the table structure on the database server required deleting the .TD files to get the updated structure. This led to unnecessary deployment headaches. We improved the efficiency of our OPEN calls so that we now get updated information from the server when the file is opened without affecting performance.


For a DataFlex program to co-exist amicably with changes made to table structures on the database server, we need to store (and retrieve) as much information on the servers as possible, without breaking DataFlex functionality.


The following are the highlights of the new version:

Store relationship information in the database
Currently, the relationship information between files is stored in the INT file. With V10.1 drivers, users will be able to recreate all DataFlex relationships directly on the server, and you will also be able to read relationship information on the server back into DataFlex.


Mixed-case table and field names
Currently we allow all object names to be either all upper case or lower case and the field names follow the convention selected for the table name. In v10.1, users will be able to define their table names and field anyway they prefer.


Inverse Key data integrity check
We are introducing a new data checker for diagnosing problems with inverse key field values


Convert tables types from recnum to RowID tables
Users will be able to create ROWID tables using VDF Studio as well as convert existing RECNUM tables to ROWID tables using our migration utility.


Save multiple connection strings in login dialog
The current login dialog box only allows users to connect to one server. With this enhancement, users will be able to switch between multiple server back ends and save the login information. This is useful in a development environment where developers have to switch between development or training server to and production server.


New SQL script for database maintenance

In addition to scripts for creating or dropping objects, the new scripts will allow analyzing and adjust database after loader executions, adjusting sequences and handling line feed characters in in text files and also scripts for turning on triggers.


Increase in ESQL performance
We have improved performance of ESQL code in retrieving data, especially when using variables to bind values.


New low-level ESQL API
Our current ESQL engine is implemented through the DataFlex ICODE engine using FMAC commands. We have built a completely new driver level API to allow building object-oriented ESQL classes for working with multiple result sets, simplifying stored procedure and function.


Tablespace control (PostgreSQL only)
Allows PostgreSQL users to select the table space where they want to create tables.

 

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Why Migrate from Btrieve to PostgreSQL and other Relational Databases?

Introduction Many independent software vendors (ISV) and corporate users still rely on applications that use a category of database collective called...

Read More
Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

Four Challenges in Converting COBOL Applications from ISAM Databases to Relational Databases

COBOL applications are the foundation of numerous essential business functions, especially within the banking, insurance, and government sectors....

Read More
Application Modernization 101: Ultimate Guide to Digital Transformation

Application Modernization 101: Ultimate Guide to Digital Transformation

Imagine breaking free from the constraints of old, monolithic systems and embracing the agility and innovation of cloud-based solutions.

Read More