FWD » Core Development » Database

02/14/2019

02:07 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter

Thanks for fixing this. Please note that @index_selection.rules@ lines 487-512 and lines 594-619 are exact duplicates... Eric Faulhaber

10:03 AM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter

Eric Faulhaber wrote:
> Ovidiu, I am concerned your changes to @index_selection.rules@ may be too aggressive. Won't ... Ovidiu Maxiniuc

09:41 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter

Ovidiu, I am concerned your changes to @index_selection.rules@ may be too aggressive. Won't this extract built-in fun... Eric Faulhaber

02/13/2019

02:54 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter

The function call seems to be more complicated. In fact, I think that all calls to UDF (ABL internal functions) are e... Ovidiu Maxiniuc

02/11/2019

03:39 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter

I did some tests today in order to understand the exact moment when the evaluation of the @P2JQuery.Parameter@ is nee... Ovidiu Maxiniuc

02/07/2019

02:36 PM Feature #3044: dynamic validation expression support

Most (if not all) of the work on this was already done in #3275 (see #3275-113 and later). Greg Shah

02/06/2019

06:05 PM Feature #3758: misc database features

I added (full) implementation of RECORD-LENGTH to 3750b. Committed revision 11340.
The solution central point is in ... Ovidiu Maxiniuc

09:52 AM Feature #3758: misc database features

Please see #3549 for my previous research into the layout of a 4GL serialized database record. It has findings that ... Greg Shah

09:16 AM Feature #3758: misc database features

3750b Eric Faulhaber

08:21 AM Feature #3758: misc database features

Eric Faulhaber wrote:
> Did you base your implementation on https://documentation.progress.com/output/ua/OpenEdge_la... Ovidiu Maxiniuc

10:40 PM Feature #3758: misc database features

Ovidiu Maxiniuc wrote:
> Do we need to find the exact formula for RECORD-LENGTH?
> I have implemented a formula tha... Eric Faulhaber

09:23 PM Feature #3758: misc database features

Eric,
Do we need to find the exact formula for RECORD-LENGTH?
I have implemented a formula that works well for a sm... Ovidiu Maxiniuc

01/28/2019

02:47 AM Feature #3758: misc database features

3750b/11317 adds basic runtime support for the {READ|WRITE}-JSON methods. Basic JSON import and export work with some... Eric Faulhaber

01/22/2019

12:16 PM Feature #3870: enhance conversion and import to make it feasible for multiple OpenEdge databases ...

Another concern is that ABL code may be written to explicitly CONNECT/DISCONNECT with a database that is to be merged... Eric Faulhaber

06:51 AM Feature #3758: misc database features

Eric Faulhaber wrote:
> What is the actual requirement in this regard? When does the transaction id need to be gener... Ovidiu Maxiniuc

01/21/2019

02:53 PM Feature #3758: misc database features

Ovidiu Maxiniuc wrote:
> The new implementation is largely based on the old code of @TransactionUpdater@, but the da... Eric Faulhaber

01:03 PM Feature #3758: misc database features

3750b was updated. The list of changes in 11303 is the following:
* added support for @CURRENT-CHANGED@, @FIND-CURRE... Ovidiu Maxiniuc

12:14 PM Bug #3896: improve performance of the _lock metadata implementation

Greg Shah wrote:
> Also, isn't the @_connect@ user-specific? If I recall, you can't see all the other user's connec... Eric Faulhaber

11:33 AM Bug #3896: improve performance of the _lock metadata implementation

All of these cases involve resources that only ever exist in limited numbers.
* transactions - one per user that i... Greg Shah

11:08 AM Bug #3896: improve performance of the _lock metadata implementation

> Can't we just enhance our current lock manager data structures to maintain enough information such that the @_lock@... Eric Faulhaber

10:46 AM Bug #3896: improve performance of the _lock metadata implementation

Most applications will almost never access the @_lock@ table. When it is used, generally it relates to a custom util... Greg Shah

10:33 AM Bug #3896: improve performance of the _lock metadata implementation

Another tweak on this idea is periodically (maybe once every minute or few minutes?) to flush the diff data to the da... Eric Faulhaber

10:22 AM Bug #3896: improve performance of the _lock metadata implementation

FWD's implementation of the @_lock@ metadata is too slow. The current implementation updates an in-memory H2 database... Eric Faulhaber

10:09 AM Bug #3896 (Closed): improve performance of the _lock metadata implementation

Eric Faulhaber

01/18/2019

09:29 AM Feature #3758: misc database features

> Where should I commit? My update is based on 3750a.
Please use 3750b. It is based on trunk 11298 (which is 3750a). Greg Shah

01/17/2019

08:02 AM Feature #3758: misc database features

Continuation:
The @DBTASKID@ function is related to @_trans@ VST. However, the relation is not 1:1. If, in a transac... Ovidiu Maxiniuc

01/16/2019

04:04 PM Feature #3758: misc database features

Status & notes:
> *BUFFER:FIND-CURRENT Method*
> Needs to be wired to existing, backing support in the persistence ... Ovidiu Maxiniuc