Smart Orders

[rdonnay]

I have questions about ISAM Orders. This is from the Alaska documentation:

ISAM Orders: These orders maintain 100% backward compatibility with traditional ISAM indexes, utilizing a special order column to represent the synthetic key value of ISAM indexes. This ensures that even user-defined functions in index expressions and complex FOR conditions work correctly.

Has anyone used this capability to incorporate legacy CDX indexes with UDF's?

What is everyone's experience with Alaska Software's support forum?
I stopped trying to get online support from Alaska years ago because nobody used their newsgroup, but the PGDBE in ISAM mode may require more support than seems to be available in the documentation.

[Tom]

Has anyone used this capability to incorporate legacy CDX indexes with UDF's?

We removed all UDFs from index expressions when we started with ADS a loooooong time ago (it began in Boise, Idaho - do you remember?). We did exactly that: Where needed, we created fields containing the result of the index expression and created the indexes on those fields.
So, we don't use this capability for UDFs, but I assume it's almost the same with all Xbase++-functions which are not supported by PostGres (and were supported by the ADS).

[k-insis]

newsgroup @alaska was left to its own decade ago; at some times they did not even knew that it was down for weeks at time ...
And there is hardly anything about pgdbe on old newsgroup, while "ILX" forum is open only to paying customers apart from 'q&a' section.

This is what Pirsig wrote about topic in 2021:

"How to make your complex SET FILTER expression work on the PostgreSQL server"

https://ilx.alaska-software.com/index.p ... server.34/

So I guess a set of stored procedures on side of postgresql is needed to exactly replicate existing local functions.

And there is also this: - class pgremote filter too:

https://doc.alaska-software.com/content ... filter.cxp

Does install of xbase compiler come with help20\pg20.chm file ?

I have questions about ISAM Orders. This is from the Alaska documentation:

ISAM Orders: These orders maintain 100% backward compatibility with traditional ISAM indexes, utilizing a special order column to represent the synthetic key value of ISAM indexes. This ensures that even user-defined functions in index expressions and complex FOR conditions work correctly.

Has anyone used this capability to incorporate legacy CDX indexes with UDF's?

What is everyone's experience with Alaska Software's support forum?
I stopped trying to get online support from Alaska years ago because nobody used their newsgroup, but the PGDBE in ISAM mode may require more support than seems to be available in the documentation.

[Tom]

So I guess a set of stored procedures on side of postgresql is needed to exactly replicate existing local functions.

No.

[rdonnay]

So I guess a set of stored procedures on side of postgresql is needed to exactly replicate existing local functions.

I think that I have already come to that same conclusion after testing performance of ISAM mode with UDF's in indexes.

There is legacy code in the customer's application that is highly dependent on these UDF indexes, therefore some routines will most likely need to be replaced with SQL Select statements and Order By <stored procedure>. I only acquired their source code this morning, so I will need to examine how these indexes are used before I make that decision. Regardless, I will be learning the language of stored procedures now.