Elevate Software


Login Login

ProductsBulletSalesBulletSupportBulletDownloadsBulletAbout





Home  Elevate Software Blog

Icon Elevate Software Blog

ElevateDB 2.26 Build 3 Released
Posted by Tim Young on Tue, Aug 15 2017

ElevateDB 2.26 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 one important bug fix, which is detailed here.

In addition, in this build the VCL product DCUs for Delphi 10.2 Tokyo are now compiled with Delphi 10.2 Tokyo Update 1.

Tags: ElevateDB, New BuildsPermanent Link 0 Comments

Elevate Web Builder 2.06 Build 5 Released
Posted by Tim Young on Wed, Jul 12 2017

Elevate Web Builder 2.06 Build 5 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.

Normally we don't add new features or enhancements in builds. But, because 2.07 is already scheduled to include the new server-side code execution and other major web server improvements, we have snuck some new features into 2.06 Build 5 instead. These new features, and some minor breaking changes, are described in the release notes:

2.06 Build 5 Breaking Changes
The following are breaking changes in 2.06 Build 5:
  • The TToolBarButton, TMenuBarItem, TMenuBarSeparatorItem, TMenuItem, and TMenuSeparatorItem control interfaces have been changed so that their Background.Fill.Color property is set to clTransparent for the Normal and Disabled states in both the default and desktop control interface sets.
2.06 Build 5 Improvements
The following are new features and enhancements in 2.06 Build 5:
  • The TGrid control now includes a AddColumnsFromDataSet method for quickly creating grid columns for all defined columns in the dataset referenced in the DataSet property.


  • The TDialog and TForm controls now include an ActivateOnClick property for use with dialogs/forms that are parented to other controls.


  • The TDialogCaptionBar control how includes a Background property.


Tags: Elevate Web Builder, New BuildsPermanent Link 0 Comments

Elevate Web Builder 2.06 Build 4 Released
Posted by Tim Young on Thu, Jul 6 2017

Elevate Web Builder 2.06 Build 4 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 Link 0 Comments

Elevate Web Builder 2.06 Build 3 Released
Posted by Tim Young on Wed, Jul 5 2017

Elevate Web Builder 2.06 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 several bug fixes, which are detailed here.

Normally we don't add new features or enhancements in builds. But, because 2.07 is already scheduled to include the new server-side code execution and other major web server improvements, we have snuck some new features into 2.06 Build 3 instead. These new features, and some minor breaking changes, are described in the release notes:

2.06 Build 3 Breaking Changes
The following are breaking changes in 2.06 Build 3:
  • The TPanelCaptionBar and TDialogCaptionBar control interfaces have changed slightly for the desktop control interface set. The Padding property has been modified so that the right padding is 10 pixels instead of 4. This provides a more balanced caption alignment for the new exposed Alignment property for caption bar captions (see new features below).


  • The import of dataset columns in the dataset columns editor in the IDE now performs a reconciliation of the columns instead of an outright replacement of the columns. If any columns exist that don't exist in the imported columns, these columns will be moved to the end of the defined columns for the dataset where they can be manually removed, if necessary. If any of the imported columns reside in a different ordinal position in the dataset, the IDE will automatically correct the position of the affected column(s) during the import.

    In addition, there is a new reset button that allows you to reconcile the columns using the existing columns in the dataset. The only restriction on performing a reset operation is that the dataset must be defined in the Database Manager. The IDE will always prompt you to select the database where the dataset is defined, but it will first attempt to scan the defined databases to find the proper database and, if it finds it, will automatically select it before prompting you to select the database.
2.06 Build 3 Improvements
The following are new features and enhancements in 2.06 Build 3:
  • The inertia scrolling support for touch environments is now complete. This support was partially completed in 2.06 Build 2, but there were some lingering issues that needed worked out. The inertia scrolling support is automatic for touch environments and defaults to behaviors that mirror the inertia scrolling in iOS, but you can use the following TApplication properties to modify the default inertia scrolling behaviors:

    InertiaScrollStyle
    InertiaScrollThreshhold
    InertiaScrollDuration


  • Support for the pointer events API is now available for browsers that support touch environments but don't implement the touch events API. The browsers that only support the pointer events API are Microsoft Internet Explorer 11 and Edge, and the affected platforms include Windows Desktop 8/8.1, 10, and Windows Phone. You don't need to do anything at all in your code to enable this support. It is automatically enabled for these environments and the OnTouch* events will simply work now in such environments.


  • The TButtonComboBox, TEditComboBox, and TGridColumn controls now include an AutoDropDown property that, when enabled, causes the drop-down control to be shown as soon as the user starts typing in the control.


  • The TToolBarButton control now includes new AllowSelection and Selected properties that allow you to specify that the button should be selectable. Being selectable allows the user to click on the button and have the button remain in a pushed state. In this state, the Selected property will return True for the applicable toolbar button. In addition, the TToolBar control now includes a MultiSelect property to specify whether multiple toolbar buttons can be selected at the same time. In total, all of these new properties allow you to create toolbars that act like sets of check boxes or radio buttons.


  • The TDialogCaptionBar and TPanelCaptionBar controls, which are part of the TDialog and TPanel controls, respectively, now include Alignment properties that specify how the caption in the caption bar should be aligned.


  • The TDialog and TPanel controls now include an OnCaptionBarDblClick event that is fired whenever the caption bar is double-clicked.


  • The TPanel control now includes OnMinimize and OnRestore events that are fired when the panel is minimized and restored, respectively.


  • The TServerRequest component now includes new RequestURL and ResponseContentType properties. Both properties are read-only and are provided as a convenience to allow for easier identification of aspects of a request that normally require extra code to retrieve. The RequestURL property represents the complete URL being used with the request, including any query parameters specified for the request. The ResponseContentType property represents the Content-Type HTTP header, if present, from the response.


  • The TServerRequest component now includes a new OnStart event. This event is triggered right before a server request is executed.


  • The TStringBuilder class now includes a new GetString method that allows you to extract a portion of the characters as a string.


Tags: Elevate Web Builder, New BuildsPermanent Link 0 Comments

ElevateDB 2.26 Build 2 Released
Posted by Tim Young on Tue, Jul 4 2017

ElevateDB 2.26 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 two important bug fixes, which are detailed here.

Tags: ElevateDB, New BuildsPermanent Link 0 Comments

ElevateDB 2.26 Released
Posted by Tim Young on Mon, Jun 26 2017

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

The complete list of breaking changes and new features is below.

2.26 Breaking Changes
The following are breaking changes in 2.26:
  • The following incident report:

    Incident Report #4528 - Altering a Table Results in an Incorrect Table Structure Checksum

    deals with an issue with incorrect checksum calculations during table alterations. This bug can affect your ability to restore backups when restoring only table files without also restoring the database catalog. However, please keep in mind that the table structure checksums are only re-computed when a table is altered in some way, and under normal operation are simply just stored and compared to ensure that the physical table files match the table structure for the table in the database catalog.


  • There is a new JOININDEXTHRESHHOLD keyword available for the SQL SELECT statement. This keyword controls how ElevateDB handles optimized (indexed) WHERE conditions on tables that are the target of INNER JOINs. For more general information, please see the How ElevateDB Selects the Rows section in the Optimizer topic in the SQL manual.

    Previously, ElevateDB would simply use any available, usable index and build a bitmap that represented the set of rows, irrespective of how many rows were selected. This works fine when there are no joins, but can be problematic when the number of rows selected is large and the table is also the target of an INNER JOIN. In such cases, the INNER JOIN condition's bitmap must constantly be assigned/ANDed with the WHERE condition's bitmap and, because the join condition's bitmap typically represents a much smaller set of rows than the WHERE condition, this process of reconciling the bitmaps becomes computationally expensive and a drag on performance.

    The value provided with JOININDEXTHRESHHOLD clause is an integer value representing a percentage of rows that, when exceeded, causes ElevateDB to treat such WHERE conditions as un-optimized row scans instead of index scans. This eliminates the computationally expensive bitmap operations and drastically improves the performance of the SELECT statement. The default value for the JOININDEXTHRESHHOLD is 75. This means that a WHERE condition must select at least 75% of the rows in a table is also the target of an INNER JOIN condition in order to be converted into a row scan.
2.26 New Features
The following are the new features in 2.26:
  • There is a new NO BACKUP FILES clause included with the ALTER TABLE, CREATE INDEX, CREATE TEXT INDEX, ALTER INDEX, ALTER TEXT INDEX, DROP INDEX, and OPTIMIZE TABLE SQL statements. This clause allows you to stop ElevateDB from retaining backup files (*.old) for physical table files after the execution of the SQL statement completes.

    Information The NO BACKUP FILES clause does not apply to physical backup files created for the database catalog, which are always created and retained. Also, if the application executing the SQL statement is killed for any reason, it is still possible for these backup files to be present and not removed.


  • There is a new FROM PUBLISHED UPDATES clause included with the CREATE TABLE statement. This clause allows you to create a table (permanent or temporary) that includes all pending published updates for all, or some, of the tables in the database.


  • Query execution can now be cancelled while ElevateDB is executing un-optimized WHERE conditions on tables. Previously, ElevateDB would need to wait until such conditions were executed before it could cancel the query execution, and could only cancel query execution while executing joins and building the result set. This design was used for performance reasons, but it resulted in situations where runaway un-optimized queries could never be killed without killing the application itself.
In addition, this release contains several bug fixes, which are detailed here.

Tags: ElevateDB, New ReleasesPermanent Link 0 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-262
Image