-
Michael Kaczmarczyk
- PowerBuilder
- Monday, 21 September 2026 09:43 AM UTC
HI,
a customer of us is complaining about performance issues after upgrading from an old version of our program ( PB2019R3 ) to the current version ( PB2022R2 ). We do data retrieval in our application and sort/filter on the clients side.
We could drill the issue down to a simple SQL query select xyz from abc where <someStatements>:
(e.g. Select rechnung.nr from rechnung where rownum <=100000)
- 100k data entries retrieved from DB -> ~1s for all Data to be shown
- 100k data entries retrieved from DB with sort="upper(left(nr)) A" -> ~3s for all Data to be shown
- 100k data entries retrieved from DB with sort="dec(nr) A" -> ~50s for all Data to be shown
nr is here a column with content like 1000-47.
Trying to compute the value dec(nr) before and using this value in the sort like
cf_nr = dec(nr)
sort="cf_nr A"
is not helping here as the needed time is the same.
We checked here already:
- no redraw is done ( we just log the result, same issue )
- data writing to a data window is not changing the issue
- PB2019R3 needs for the same query ~13s
- PB2025R2 needs for the same query ~ 50s ( same as PB2022R2 )
- Accessibility=0 -> not applicable here for this case ( mentioned: https://docs.appeon.com/pb2025/troubleshooting_guide/tr_011.html )
Is there something we can do? Is the issue known? Because having a time of around 50s is nothing our customer will accept. The time before with ~ 13s would be ok, less of course better.
The google AI mentions that there is now an overhead because of more strict handling of the dec-cast. But I have not found anything related to it directly in the appeon documentation.
Kind regards,
Michael
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.