Open Sjoerd82 opened 4 years ago
Update: When I instead of using IndexedDB, use regular objects it works fine. So, it is definitely IndexedDB related.
what happens if you only do the 'ATTACH INDEXEDDB DATABASE mydatabase; \ USE mydatabase;
once?
what happens if you seperate the attach and use part into each own so its
alasql(['ATTACH INDEXEDDB DATABASE mydatabase;', 'USE mydatabase;', qQueryA,qQueryB]) .then( result => { console.log(result) })
(and remove the attach and use part of the queries)
I'm brand new to alaSQL, so forgive me if this is a known bug (couldn't find it though), or if I'm doing this wrong..
I have a query that does a UNION on a few IndexedDB tables. This fails with a weird error, so I thought, OK, let just split them into two queries and I'll combine the arrays in JS. If I simply fire either one of the queries it works, but when I fire both queries, I get the same error.
This fails: alasql([qQueryA,qQueryB]) .then( result => { console.log(result) })
This fails, unless I comment one out: alasql.promise(qQueryA) .then( result => { console.log(result) }) alasql.promise(qQueryB) .then( result => { console.log(result) })
The error is: Uncaught TypeError: Cannot read property '-1630748626' of undefined
Since this is IndexedDB, I probably cannot do these synchronously as a temporary workaround...?
On a side note, I had to specify: AND NOT asoc_cp.tableD_id IS NULL
To avoid inner joining NULLs, kinda unexpected?