Elevate Software


Login Login

ProductsBulletSalesBulletSupportBulletDownloadsBulletAbout





Home » Elevate Software Blog

Icon Elevate Software Blog

Elevate Web Builder 2.06 Build 13 Released
Posted by Tim Young on Sun, May 20 2018

Elevate Web Builder 2.06 Build 13 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions. This build contains several bug fixes, which are detailed here.

Tags: Elevate Web Builder, New BuildsPermanent Link0 Comments

DBISAM 4.45 Build 3 Released
Posted by Tim Young on Thu, May 17 2018

DBISAM 4.45 Build 3 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

This build contains a bug fix for an outstanding issue with write lock timeouts:

# 4639 Table Locking Using Incorrectly-Calculated Internal Timeout Values


Tags: DBISAM, New BuildsPermanent Link0 Comments

DBISAM 4.45 Build 2 Released
Posted by Tim Young on Tue, May 15 2018

DBISAM 4.45 Build 2 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

This build contains a few bug fixes, which are detailed here.

Tags: DBISAM, New BuildsPermanent Link0 Comments

Elevate Web Builder 2.06 Build 12 Released
Posted by Tim Young on Thu, May 10 2018

Elevate Web Builder 2.06 Build 12 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions. This build contains several bug fixes, which are detailed here.

Tags: Elevate Web Builder, New BuildsPermanent Link0 Comments

ElevateDB 2.28 Released
Posted by Tim Young on Wed, May 2 2018

ElevateDB 2.28 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

The breaking changes and new features for the ElevateDB VCL/LCL, DAC, and PHP products are below. In addition, this release contains several bug fixes, which are detailed here.

2.28 Breaking Changes for VCL/LCL Products
The following are breaking changes in 2.28:
  • Large file support is now enabled by default in ElevateDB. Along with this change, the TEDBEngine LargeFileSupport and TEDBSession LocalLargeFileSupport properties have been removed.

    These are published properties, so please be sure to open, ignore any warnings about these properties being absent, and re-save any forms or data modules that use the TEDBEngine or TEDBSession components to ensure that you do not see any runtime missing property errors in your application(s).

    Warning If you are using local ElevateDB sessions to directly access shared databases on a file server, you need to make sure that all client applications that are accessing the data are either updated to 2.28 or have their pre-2.28 TDBISAMEngine LargeFileSupport and/or LocalLargeFileSupport properties set to True. Failure to do so can cause the local ElevateDB sessions to not see each other's locks, which can lead to database corruption.


  • The TEDBEngine ExclusiveFileAccess property has been removed and replaced with the TEDBEngine BufferedFileIO property. Please see the new features in 2.28 section below for more information on the new buffered file I/O functionality in ElevateDB.
2.28 New Features for VCL/LCL Products
The following are the new features in 2.28:
  • ElevateDB now includes new global buffered file I/O functionality. There are new TEDBEngine BufferedFileIO, BufferedFileIOSettings, and BufferedFileIOFlushInterval properties for configuring the buffered file I/O in the engine. Please see the Buffering and Caching topic in the SQL manual for more information.


  • ElevateDB now includes new SQL statement and function/procedure caching functionality. There are new TEDBSession SQLStmtCacheSize and FuncProcCacheSize properties for configuring the caching, as well as the TEDBSession FreeCachedSQLStmts and FreeCachedFuncProcs methods for freeing cached SQL statements and functions/procedures. Please see the Buffering and Caching topic in the SQL manual for more information.


  • There are two new system information tables, the FileIOStatistics table, and the SessionStatistics Table table.


  • There is a new CURRENT_SESSIONID function for returning the current session ID in SQL/PSM routines.
2.28 Breaking Changes for DAC Products
The following are breaking changes in 2.28:
  • Large file support is now enabled by default in ElevateDB. Along with this change, the LARGEFILESUPPORT connection attribute has been removed.

    Warning If you are using local ElevateDB sessions to directly access shared databases on a file server, you need to make sure that all client applications that are accessing the data are either updated to 2.28 or have their pre-2.28 LARGEFILESUPPORT connection attributes set to True. Failure to do so can cause the local ElevateDB sessions to not see each other's locks, which can lead to database corruption.
2.28 New Features for DAC Products
The following are the new features in 2.28:
  • ElevateDB now includes new global buffered file I/O functionality. Please see the Buffering and Caching topic in the SQL manual for more information.


  • ElevateDB now includes new SQL statement and function/procedure caching functionality. There are new STMTCACHESIZE and PROCCACHESIZE connection attributes for configuring the caching, as well as the EDBConnection FreeCachedStatements and FreeCachedProcedures methods for freeing cached SQL statements and functions/procedures in the ElevateDB .NET Data Provider (there are no equivalents for the ElevateDB ODBC Driver. Please see the Buffering and Caching topic in the SQL manual for more information.


  • There are two new system information tables, the FileIOStatistics table, and the SessionStatistics Table table.


  • There is a new CURRENT_SESSIONID function for returning the current session ID in SQL/PSM routines.
2.28 Breaking Changes for PHP Products
The following are breaking changes in 2.28:
  • Large file support is now enabled by default in ElevateDB. Along with this change, the LARGEFILESUPPORT connection attribute has been removed.

    Warning If you are using local ElevateDB sessions to directly access shared databases on a file server, you need to make sure that all client applications that are accessing the data are either updated to 2.28 or have their pre-2.28 LARGEFILESUPPORT connection attributes set to True. Failure to do so can cause the local ElevateDB sessions to not see each other's locks, which can lead to database corruption.
2.28 New Features for PHP Products
The following are the new features in 2.28:
  • ElevateDB now includes new global buffered file I/O functionality. Please see the Buffering and Caching topic in the SQL manual for more information.


  • ElevateDB now includes new SQL statement and function/procedure caching functionality. There are new STMTCACHESIZE and PROCCACHESIZE connection attributes for configuring the caching, as well as the edb_freecachedstmts and edb_freecachedprocs functions for freeing cached SQL statements and functions/procedures. Please see the Buffering and Caching topic in the SQL manual for more information.


  • There are two new system information tables, the FileIOStatistics table, and the SessionStatistics Table table.


  • There is a new CURRENT_SESSIONID function for returning the current session ID in SQL/PSM routines.


Tags: ElevateDB, New ReleasesPermanent Link0 Comments

DBISAM 4.45 Released
Posted by Tim Young on Mon, Apr 30 2018

DBISAM 4.45 is now available for download. If you're an existing customer, then you should be receiving an email shortly with download instructions.

The breaking changes and new features for both the DBISAM VCL and ODBC products are below.

4.45 Breaking Changes for VCL Products
The following are breaking changes in 4.45:
  • The TDBISAMEngine LargeFileSupport property has been removed and large file support is now always on. This functionality has its roots in the old Windows 9x series of operating systems and is no longer relevant.

    Warning If you are using local DBISAM sessions to directly access shared databases on a file server, you need to make sure that all client applications that are accessing the data are either updated to 4.45 or have their pre-4.45 TDBISAMEngine LargeFileSupport property set to True. Failure to do so can cause the local DBISAM sessions to not see each other's locks, which can lead to database table corruption.


  • The TDBISAMSession PrivateDir property has been changed from being a published property to a public property, so you may see a missing property error when loading forms or data modules in the IDE that contain the TDBISAMSession component after updating to 4.45. This property is typically only useful at run-time, and setting it at design-time could cause run-time errors if its value did not work properly with the target operating system's configuration.

    Information To make sure that you don't experience any "missing property" exceptions at run-time in your application, please open any forms or data modules in your application that contain an existing TDBISAMSession component at design-time, ignore any "missing property" errors, and then re-save the owner form(s) or data module(s) that contain the TDBISAMSession component(s).


  • The TDBISAMEngine TableReadLockRetryCount, TableReadLockWaitTime, TableTransLockRetryCount, TableTransLockWaitTime, TableWriteLockRetryCount, and TableWriteLockWaitTime properties have been replaced with the equivalent TableReadLockTimeout, TableTransLockTimeout, and TableWriteLockTimeout properties.

    Information To make sure that you don't experience any "missing property" exceptions at run-time in your application, please open any forms or data modules in your application that contain an existing TDBISAMEngine component at design-time, ignore any "missing property" errors, and then re-save the owner form(s) or data module(s) that contain the TDBISAMEngine component.
4.45 New Features for VCL Products
The following are the new features in 4.45:
  • The SQL join performance has been improved by up to 30-40%, depending upon how join-intensive the SQL being executed is. For example, SQL SELECT statements that contain INNER JOINs but no WHERE clauses are very join-intensive, and will benefit the most from this performance improvement.


  • The internal bitmap set handling for filters and SQL has been changed so that DBISAM uses sparse bitmaps instead of linear bitmaps, resulting in faster performance and less memory consumption. Part of the join performance improvements mentioned previously are due to the use of the new sparse bitmaps.


  • The sockets functionality in the DBISAM engine has been replaced with a new implementation, which should result in better overall performance and stability for remote sessions and the database server.


  • There is a new NOWHEREJOINS clause available for the SQL SELECT, UPDATE, and DELETE statements. This clause allows you to prevent DBISAM from treating any inner joins in the WHERE clause (SQL-89-style joins) as optimized joins, instead allowing the expressions to be treated as un-optimized expressions that will be evaluated after any joins are executed.


  • There are new TDBISAMEngine StoreActive, TDBISAMSession StoreActive, TDBISAMDatabase StoreConnected, TDBISAMTable StoreActive, and TDBISAMQuery StoreActive properties for specifying whether the component's related Active and Connected properties are stored in the owner form or data module.
4.45 Breaking Changes for ODBC Products
The following are breaking changes in 4.45:
  • The large file support driver configuration option has been removed and large file support is now always on. This functionality has its roots in the old Windows 9x series of operating systems and is no longer relevant.

    Warning If you are using local DBISAM ODBC Driver connections to directly access shared databases on a file server, you need to make sure that all client applications that are accessing the data are either updated to use the 4.45 DBISAM ODBC Driver or turn on the pre-4.45 large file support driver configuration option turned on by using the ODBC Driver Configuration Utility that is included with the DBISAM ODBC Driver installation. Failure to do so can cause the local DBISAM sessions to not see each other's locks, which can lead to database table corruption.


  • The DBISAM ODBC Driver Table Read Lock Retry Count, Table Read Lock Wait Time, Table Transaction Lock Retry Count, Table Transaction Lock Wait Time, Table Write Lock Retry Count, and Table Write Lock Wait Time driver configuration options have been replaced with Table Read Lock Timeout, Table Transaction Lock Timeout, and Table Write Lock Timeout configuration options. These options can be modified using the ODBC Driver Configuration Utility that is included with the DBISAM ODBC Driver installation.
4.45 New Features for ODBC Products
The following are the new features in 4.45:
  • The SQL join performance has been improved by up to 30-40%, depending upon how join-intensive the SQL being executed is. For example, SQL SELECT statements that contain INNER JOINs but no WHERE clauses are very join-intensive, and will benefit the most from this performance improvement.


  • The internal bitmap set handling for filters and SQL has been changed so that DBISAM uses sparse bitmaps instead of linear bitmaps, resulting in faster performance and less memory consumption. Part of the join performance improvements mentioned previously are due to the use of the new sparse bitmaps.


  • The sockets functionality in the DBISAM engine has been replaced with a new implementation, which should result in better overall performance and stability for remote sessions and the database server.


  • There is a new NOWHEREJOINS clause available for the SQL SELECT, UPDATE, and DELETE statements. This clause allows you to prevent DBISAM from treating any inner joins in the WHERE clause (SQL-89-style joins) as optimized joins, instead allowing the expressions to be treated as un-optimized expressions that will be evaluated after any joins are executed.


Tags: DBISAM, New ReleasesPermanent Link0 Comments


Previous Entries: 1-6 7-12 13-18 19-24 25-30 31-36 37-42 43-48 49-54 55-60 61-66 67-72 73-78 79-84 85-90 91-96 97-102 103-108 109-114 115-120 121-126 127-132 133-138 139-144 145-150 151-156 157-162 163-168 169-174 175-180 181-186 187-192 193-198 199-204 205-210 211-216 217-222 223-228 229-234 235-240 241-246 247-252 253-258 259-264 265-270 271-276 277-282 283-288 289-294 295-300 301-306 307-312 313-318 319-324
Image