I’m getting reports of an exception that makes no sense to me. I’m getting a DatabaseException with the message another row available on the line Var Rows As RowSet = SelectSQL("SELECT * FROM maps ORDER BY official DESC, sort;").
This is one of the least helpful errors I’ve ever seen. I also haven’t been able to reproduce it myself, this is coming from my automated reporter. It’s also pretty new, though my IDE version has not changed. This is likely to be something to do with the database and not a Xojo bug, but I don’t understand the error. I don’t know what to look for. And Google has not been helpful.
Just grasping here, but maybe not really an error and shouldn’t throw an exception; see the SQLite docs for: Result and Error Codes (is 100 the result code in the error?) and also the note at the bottom here (under “goofy interface alert”): Evaluate An SQL Statement
Sounds like that could be it. I don’t have the error number logged, but I guess I should add that. If this is a “not-really-an-error” error, I’ll have to find a way to reproduce this reliably to convince Xojo to fix it. Too early to tell though, since I’m not certain that’s what is going on.
The semicolon is not required, though I usually include it. I did doctor the line a little because the original is Self.SQLSelect. It’s a custom subclass that gave me API2-like features before API2. That isn’t important to the issue though, so I chopped that off, but should have replaced it with something.
Right but we’re talking about SQLite. The semicolon is implied at the end of the string. I do normally use it because it’s good practice, but it’s just forgotten here. The code works 99.99% of the time. If it were an issue with the wildcard, ordering, or semicolon, I’d see it every time. Plus, SQLite is more forgiving about ordering by columns that were not selected.
As @Matthew_Dinmore suggested
If the error code is 100, it’s a result code of “(100) SQLITE_ROW”
which indicates there is another row to step, so it’s probably a xojo bug that’s not handling the stepping ?
(step = MoveToNextRow or For each… iterate ?)
Maybe they are using the legacy code? not sure how the sqlite 3 is implemented in xojo but it sounds like you sould NOT get that exception… (since it’s a result code, not an error)
Correct me if i’m wrong, this is how i read it from the docs of sqlite
For now the best I can do is add the error number to the exception message and wait for it to trigger next time I make a build. But yes I agree that this is feeling like something that Xojo will need to fix.
I doubt it. I’m not even seeing it, and I spend boatloads of time in the app. In this case my had been released for about a week and downloaded hundreds of times in that period before anybody ran into the issue. My exception reporting is 100% automated, so this isn’t even a case of somebody hitting it and failing to report. So whatever is happening is exceptionally rare. It’s not an issue I’d call a showstopper, but it’s definitely a curiosity.