Open mandel opened 2 years ago
Im on it
It is a very interesting areas where AlaSQL is stepping in the two worlds of NULL...
The programming language null is a value but database null is not a value.
I found great joy in reading this a while ago: https://arxiv.org/html/1606.00740
@piotr-m-bielski this will likely be a breaking change. I suggest we identify how to solve it, and then consider if its possible to make an option to use the old way or the SQL way.
Okey, so let me know when you make decision how to do it.
Oh - we can work on a solution. So you can just start on this. But before the release we will discuss how to let the users configure this. How we do that depends on what the solution looks like. So I suggest you work on solving this, and then we talk about how the solution can be part of what Alasql offers.
@piotr-m-bielski Have you had a chance to dive into this? Any ideas?
I tried to do that, but It is really hard to understand how it works. (parser) Variables like yy do not help. I will try again over this weekend
In agree. Its a nasty beast to dive into.
In short: the compiler makes an AST. The AST is transformed into a string of the javascript doing all the things needed to execute the SQL. Then the string is run with data as parameters.
NULL has a sad story in AlaSQL with the original design not tapping into its power, but treating undefined
and null
as kind of the same.
You can also have a look at https://github.com/AlaSQL/alasql/issues/1415#issuecomment-1293335079 for some inputs regarding diving into the code.
I give up.
Thank you for trying.
Di you find out anything interesting? Any thoughts to share?
My friend and I plan on working on this and issue 1415 (union operator not working). Any advice before we get started?
@aotru Thank you so much.
Advice: Make a test first that illustrates the problem.
You might also benefit from the suggestions in this this comment about one way of running alasql with breaks and steps: https://github.com/AlaSQL/alasql/issues/1415#issuecomment-1293335079
Any luck @aotru ?
Try using the join concept, to get the expected output.
Hi,
We have noticed that the result of the following example doesn't return the expected result (based on https://doi.org/10.14778/3151113.3151116)
See https://jsfiddle.net/3ya794kr/.
This query compares each row of
R
withNULL
which always returnsunknown
in SQL. Sincenot in unknown
isunknown
, the result should be the empty collection.