AlaSQL version: very old?

Hi! I am having issues with AlaSQL, it seems to be on a very old version. Running

console.log("AlaSQL version: ", alasql.version);
return alasql.version

gives me

"0.4.5-develop-1587"

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.

Thank you :slight_smile:

Unfortunately there are few libraries, components that are outdated and haven't been updated in a while.

To name a few:

  • AlaSQL
  • MapBox
  • Stripe component
  • JSON Schema Form (still doesn't support Patterned Properties)

Hoping we can aggregate some of these and get an update :pray:

2 Likes

Any idea when AlaSQL will be upgraded?

I attempted to work around this by adding the following to my app libraries, and it worked.

https://cdnjs.cloudflare.com/ajax/libs/alasql/4.17.3/alasql.min.js

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.

1 Like

UPDATE: For anybody interested, another native workaround is to use UNION/UNION ALL in combination with the CORRESPONDING keyword.


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. :+1:

1 Like