-
Notifications
You must be signed in to change notification settings - Fork 191
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
SQLite SELECT Query Error if record not found. #895
Comments
@jonasmalacofilho will you take a look? |
Can't reproduce it locally.
Will need a minimal reproduceable example as well as Haxe and Hxcpp versions. Probably best to mention the OS in use as well. |
Sure, I will post the code when I am able to get back into the office. To clarify, as pointed out in the subject, the error is incurred when the record is not found. It works on Neko, but for cpp we had to work around it with try/catch. hxcpp 4.0.64, haxe 4, windows 10 |
Ok, by changing to your hxcpp version I can also reproduce the problem. It's something that has already been fixed, but the patch hasn't reached a stable hxcpp release yet: #856 ("Handle .length and .nfields on empty result sets"). The fix is already available on the master branch, so if you manually install (and build) hxcpp from git you should be set. Please point me in the correct direction when you ping me for something that you know has been solved. Even if I'm the author of a commit that fixes something doesn't mean that I'll immediately remember about it, and I can easily spend a bunch time rediscovering the same fix again. |
Sorry, I didn't mean to waste your time, thanks so much for the quick reply. |
Don't worry about it. And @sonygod, perhaps I ended up being more harsh than I intended. Please don't worry too much about it either. |
@jonasmalacofilho ,sorry for delay . I post my code here |
"Invalid sqlite result" error when I check to see if the result length is >0. Works right on other platforms. Should I be handling this differently or is this a bug?
The text was updated successfully, but these errors were encountered: