Any attempt to execute a SELECT statement with 32 or more UNION ALLs in UltraliteJ for Android crashes the application. I've been using the UltraliteJ for Android 16.0.0.1823. Is there any solution/EBF/workaround for it?
|
The crash is fixed in 16.0.0.2141 or later. UltraLite will not be able to deal with a query with that many UNION's. A ULjException will be thrown with SQL error code SQLE_RESOURCE_GOVERNOR_EXCEEDED. Sorry about the long delay, as this issue got lost in the backlog. Thanks @Andy! Great news =] Is this EBF already released? If so, where can I download it?
(19 Jun '15, 12:48)
Alex
Replies hidden
@Andy Quick Can you convert it as an answer so I can close this ticket?
(13 Mar '17, 14:30)
Alex
Replies hidden
Now you can:)
(14 Mar '17, 03:57)
Volker Barth
1
Good news: the latest EBF (or SP, whatever) for Windows I've downloaded is 16.0.0.2419, so yes, it's available. But you'll need a valid S-ID (SAP support login) to download the update from https://support.sap.com/home.html
(14 Mar '17, 07:42)
Reimer Pods
|
Wow, this issue seems like a critical one for mobile app developers in usa. The Select command with 32 UNION ALLs causing a crash is definitely something that demands immediate attention. It's essential for developers to dig deep into the codebase, analyze the execution flow, and possibly consider optimizing the query or finding alternative solutions. This kind of troubleshooting showcases the importance of rigorous testing and optimization, especially in resource-constrained environments like Android. Kudos to the team for tackling this head-on and paving the way for more robust and stable applications in the future. |
I don't use Ultralite, but wouldn't it be possible to replace the front-end UNIONs by having a back-end view or procedure with the UNIONs, thereby allowing you to use a much simpler query on the front-end? 1
@SethRich, the Ultralite doesn't provide SQL procedures or views. Also, we've been developing a product with a configurable database/query engine to provide DataSource for configurable components. So, the engine must be as reliable as the Ultralite is. We don't care if the Ultralite doesn't provide such a feature like this, as long it doesn't crash the application.
(13 Aug '14, 13:06)
Alex
|
It may help if you post your query and relevant schema.
Question edited with the query. In fact, any query, no matter which schema is used, will crash the app.
It's likely that UL has a limit on the number of unions in a query -- an arbitrary (but assumed reasonable) limit for the sake of efficiency otherwise. 32 does seem like a lot of unions, but increasing it could be possible as well.
It should not crash in any case of course. That must be a separate bug which we will try to address in the near term.
Tks Tim. You've got my point. In our case, all we don't want is an application crash. We'll look forward a bug fix. For now, thank you by your attention.
Tim, any news about a bug fix?
Hi Alex,
It's still in the queue given some major release work here. I will post back when it's done. Thank you for your patience :-)
Ah, ok. Don't need to hurry up with it. It's just a minor fix. Just let me know when it is fixed. Thank you =]
Hello, Tim. Any news about this issue?