investigate performance improvement by using new executemany about simple-oracledb HOT 10 CLOSED

it will be true once i feel its stable enough and well tested (my code i mean)

from simple-oracledb.

implemented in 1.2.1

from simple-oracledb.

How do you find the performance compared with your old implementation?

from simple-oracledb.

actually having some issues making it work. I'll have to stop in the middle and continue this later on... strange however that i'm getting an error which i'm not sure what exactly it means since it is not pointing to which field in which insert/update command.
this is the error:
"NJS-011: encountered bind value and type mismatch", // errBindValueAndTypeMismatch

will have to understand what i'm doing wrong, but might take a while as I no longer have access to oracle and I run tests via docker in travis which takes forever.

from simple-oracledb.

Check the examples closely. Ping us if you have questions.

from simple-oracledb.

@cjbj finally published a version that supports executeMany (sorry it took so long).
next steps is to actually compare performance between the two and get some idea the performance impact of each.

from simple-oracledb.

Nice!

It would have been great if options.useExecuteMany could have defaulted to true. Maybe once you've checked the performance benefits ...?

from simple-oracledb.

@sagiegurari how it's going?

from simple-oracledb.

executeMany is now turned on by default.

from simple-oracledb.

Yay!

from simple-oracledb.