-
Notifications
You must be signed in to change notification settings - Fork 161
Select calls get called twice #97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I see four ways to fix this: We can delete the To avoid breaking existing code, we could keep the reset and manually set On the other hand I do not really know why reset sets We can use I will try to prepare a pull request for the last approach. What do you think? |
Part of why i didnt fix it after tracking it down is that i could not explain why that change happend and wanted to take a closer look or have someone that knows why to tell me why ;). And without #96 its hard to write a test to check for that in the future so i guess that's a plus point for #96 already. As i wrote the initial Prepared statement implementation im all for the "breaking" change that restores the behavior outlined in the README, i dont see it a breaking change its a bugfix for undefined behavior. I do have some time now and would fix it that way if its ok with you. |
- Used getter setter for all uses of execution_started - removed reset() call from _extract* - added exception for reexecution of already used statment
#97 will fix this but Travis broke, anyone got a clue about that? |
I have restarted the Travis build, but the main problem is, that in the prepared statement test we assume that |
hm thats bad, i will take a look in a moment. |
Fixed by #98 |
Hi,
while implementing my little Logger feature i noticed that i get to many sqlite_step calls, it looks like the
_extract
methods usereset()
at the end and in doing so resetexecution_started
which leads to another execution of the query when it leaves the scope.I would fix it but i lack the time right now to test it and i think thats an urgent one to fix.
The text was updated successfully, but these errors were encountered: