Andrea Giammarchi

I think this bug would better be in MicroPython repository using the `WebAssembly/PyScript - ` prefix as we're not working on MicroPython in here.

this looks pretty bad … in order to help ASAP I wonder if you could: - tell me which version of dblite you are using - give me a basic...

I've quickly done some test and it looks to me the callback is consistently fired as expected when the error occur, and such error is reported. I hav updated the...

another example would be: ``` javascript db .on('error', function(err) { console.log('something terrible happened, rebooting', err); process.exit(); }) .query('INSERT INTO users (id,email) VALUES(?,?)', [1, '[email protected]']); .query('SELECT * FROM users WHERE id=?',...

FYI .. it looks like Travis CI is having similar issue with node 0.8, but green lights on node 0.10

OK, first of all it will take some time to find out a good solution here since it's inconsistently reproducible in different envs … but I want to find the...

unfortunately reading special SQL syntax is not an option .. I really don't want to put a whole SQLite parser in here 'cause that would not follow the `dblite` KISS...

I don't have race conditions and I am unable to reproduce them everywhere I've tried :-/ Anyway, the older version is not compatible with callbacks with two arguments, so it...

What's fixed there is that the `err` you receive in the callback will be eventually an `Error` with its `message` property telling you what kind of error it was, instead...

sorry @dronus , I thought it was resolved since 2014 and closed it during some gardening. I'll keep it open and try to find out time to fix this.