Activity
From 01/21/2019 to 02/19/2019
02/19/2019
- 02:14 PM Feature #3758 (Closed): misc database features
- 01:14 PM Feature #3758: misc database features
- Greg Shah wrote:
> Can this task be closed?
RECORD-LENGTH: I think I covered all datatypes which can be serialize... - 12:44 PM Feature #3758: misc database features
- Can this task be closed?
- 12:43 PM Feature #3758: misc database features
- Code Review 3750b Revision 11340
I'm good with the changes. I like the approach with the BDT @getSize()@. When w... - 01:04 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Yes, I think it is safe.
- 01:00 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Ovidiu Maxiniuc wrote:
> I think it ready for the final regression test. It must be the ETF, the standard tests on d... - 12:29 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Greg Shah wrote:
> Does the customer's testcase work properly?
Yes, it did.
> Is there anything more to do on th... - 12:27 PM Feature #3761: add DYNAMIC-FUNCTION() support to the dynamic database WHERE clause interpreter
- Is there anything more to do on this task?
Does the customer's testcase work properly?
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...
- 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 ... - 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...
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...
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...
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).
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 ... - 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 ...
- 09:16 AM Feature #3758: misc database features
- 3750b
- 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... - 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... - 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...
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...
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...
- 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...
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... - 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... - 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... - 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... - 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@...
- 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...
- 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...
- 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...
- 10:09 AM Bug #3896 (Closed): improve performance of the _lock metadata implementation
Also available in: Atom