Try-catch errors with misspelling in SQL

[addlistener]

@mathiasrw Check it out. You can fork it to see the error messages.

The server breaks when there's no such function. Ideally it should be caught by the try block.

https://replit.com/@jchnxu/DeficientSubstantialSystemsanalysis#index.js

[mathiasrw]

Hmm. I cant replicate this. Any chance you can make a jsfiddle with it? https://jsfiddle.net/8brvex4f/

I dont understand where use median - and what is wrongFuncName(email_domain)?

---

Bonus info
Alasql is async and returns a promise if you call alasql.async or if you put the first argument in an array, or if you engage with a file like CSV or excel. So instead of the function in the second parameter you can do something like

app.use(async ctx => {
  ctx.body = 'Hello World';
  const { columns, data: objects } = await alasql.promise("SELECT RECORDSET wrongFuncName(`email_domain`) FROM CSV('some.csv') AS `temp`")
  });
});

[addlistener]

OP edited. Sorry for my vague description.

@mathiasrw And thanks for the bonus. I tried alasql.promise and it's the same bug.

[mathiasrw]

Might be related to #1491 - try v2.1.5 and see if that helps

[addlistener]

I updated the dep to 2.1.5 and it's still breaking.
https://replit.com/@jchnxu/DeficientSubstantialSystemsanalysis#index.js

I ask not because there's a bug in the median function but for a generic way to handle typos in functions. If I mistype the function name it should not bring my server down. Instead I should be able to catch the error.

[mathiasrw]

Ahhhhhh. I got it now. Its probably because the execution is run in a new Function context. Hmm. Should be doable...

[Chaitanyaprasad60]

Hi, Seems like issue is not yet resolved. Can you assign it to me?

[Chaitanyaprasad60]

I found a way to catch the error and due to this, the server will not go down. But I am unable to return the error through the callback function. As "cb" is not available in the scope of the function. Any ideas ??

[mathiasrw]

What function does not have the callback avaliable?

[Chaitanyaprasad60]

yy.Select.prototype.compileSelect2 This Function. Where the error is actually occurring

[mathiasrw]

Fix released as part of v4.1.5