Hi.
Thanks; we decided to create an index on @ID; QUERY.INDEX works very fast.
On Saturday, 15 August 2020 at 00:32:34 UTC+2 cliff...@gmail.com wrote:
> JBase indexes are very stable. We have about 145 throughout all of our
> tables.
>
>
>
> On Friday, July 31, 2020 at 11:15:36 AM UTC-4, VK
JBase indexes are very stable. We have about 145 throughout all of our
tables.
On Friday, July 31, 2020 at 11:15:36 AM UTC-4, VK wrote:
>
> Hi coleagues.
>
> What is the fastest way to SELECT a set of records from a J4 table:
>
> @IDs are in the format:
Thanks to everyone who responded.
On 02/08/2020, Marco Manyevere wrote:
> Hi,
>
> As far as I can see, the entire table will always be scanned in this case.
> This is one situation in which a prior analysis of the range arguments may
> be helpful. Assuming that you are doing this inside a
Hi,
As far as I can see, the entire table will always be scanned in this case.
This is one situation in which a prior analysis of the range arguments may
be helpful. Assuming that you are doing this inside a subroutine, it may be
worthwhile to check the difference between start and end dates (in
In an RDBMS yes, on jBASE (MV platforms) you have to create an index.
Sent from my iPhone
> On Aug 1, 2020, at 8:51 AM, VK wrote:
>
>
> Sorry forgot to mention that there's no field with account number, it's just
> a part of @ID. Isn't @ID a primary index itself?
>
>
>> On Friday, 31
Sorry forgot to mention that there's no field with account number, it's
just a part of @ID. Isn't @ID a primary index itself?
On Friday, 31 July 2020 17:15:36 UTC+2, VK wrote:
>
> Hi coleagues.
>
> What is the fastest way to SELECT a set of records from a J4 table:
>
> @IDs are in the format:
> If you consider that 3000 plus banks used JBase before it moved on, I'd
say the case for JBase indexing is solid
how many of them used jBASE and not Oracle / DB2 /MSSQL etc - maybe 10%?
how many of these 10% used jBASE indexing?
If indexing was solid why Temenos uses CONCAT files and (IIRC)
I would make the SELECT field specific, ie SELECT WITH ACCOUNT = "5001" AND
WITH DATE GT @18628 AND DATE LT 23012
ACCOUNT_NUMBER and DATE are likely to be indexed.
It's like having a porsche in the garage but insisting on using your
daughter's bicycle to do the speed trial if you insist on
Hi coleagues.
What is the fastest way to SELECT a set of records from a J4 table:
@IDs are in the format: (account_number)-(date_in_internal_format), e.g.
5001-18628.
trying:
SELECT THE.TABLE WITH @ID BETWEEN "5001-18628" "5001-23012"
Result is bit more than a second (Windows 2019 server,
