How come it's on such an old version? The latest version is 4.6.1, any plans on updating? Is there a possibility to update manually?
(I posted a similar question in an old thread here.
Is there any side effect of doing this that I should be aware of? I assume the answer is "yesโ, but what those side effects are, are unknown, since Retool likely hasnโt tested with a modern version of this library.
In this case, inspecting alasql.version is a little misleading because we actually bundle a forked version in the frontend that specifically supports running in a sandboxed iframe. It doesn't have full feature parity, but certainly has continued to receive intermittent updates.
To your point, @lkiss, I'm not sure what the implications of specifying a newer out-of-the-box version might be. Is there specific functionality or syntax that you're trying to use?
There was a bug fixed in version v4.11.0. Adding the library to the app libraries with a version >= v4.11.0 worked for me. But I also donโt know the implications of doing so. Thus far I havenโt noticed anything.
Good to know! I'll tentatively mark your post as a "Solution" in the sense that it's a functional workaround, but leave the topic itself open. Let us know if you run into any compatibility issues.
I'll also look into patching the AlaSQL fork - the fix looks pretty trivial.