Sign in to follow this  
Followers 0
mikkokh

Problems with _SQLite_FetchData()

6 posts in this topic

#1 ·  Posted (edited)

Hi.

I have large script, about 3600 lines. After updating to AutoIt 3.3.0.0 from 3.3.2.0, I get different result with _SQLite_ErrMsg() after executing of _SQLite_FetchData() command.

With AutoIt v3.3.0.0...

_SQLite_ErrCode() returns "100"

_SQLite_ErrMsg() returns "not an error"

And with AutoIt v3.3.2.0...

_SQLite_ErrCode() returns "100"

_SQLite_ErrMsg() returns "unknown error"

So, is _SQLite_ErrCode()'s result "100" error or is it not? And what that error code means?

Thanks.

Edited by mikkokh

- miXza-81 -

Share this post


Link to post
Share on other sites



It may have changed as the version of SQLite included with AutoIt was updated (see Version History in the help file). According to the SQLite web site, a return code of 100 = sqlite3_step() has another row ready. Can you post a short demo that creates a small DB in memory and performs an operation that produces the results you describe for _SQLite_ErrCode() and _SQLite_ErrMsg()?

;)


Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law

Share this post


Link to post
Share on other sites

...Can you post a short demo that creates a small DB in memory and performs an operation that produces the results you describe for _SQLite_ErrCode() and _SQLite_ErrMsg()?

;)

Hi.

Thanks about answer!

Here is one short and messy demo with that same problem...

demo.au3


- miXza-81 -

Share this post


Link to post
Share on other sites

I think the operable part is in SQLite C Interface: Error Codes And Messages:

The sqlite3_errcode() interface returns the numeric result code or extended result code for the most recent failed sqlite3_* API call associated with a database connection. If a prior API call failed but the most recent API call succeeded, the return value from sqlite3_errcode() is undefined.

It's just not valid to get error codes and messages when no error has occured. You should only be checking errors when the performed function returns <> $SQLITE_OK:
_SQLite_FetchNames($hQuery, $aNames)
MsgBox(0, "code -> 'msg'", StringFormat("%-10s  %-10s  %-10s  %-10s", $aNames[0], $aNames[1], $aNames[2], $aNames[3]))
While 1
    $RET = _SQLite_FetchData($hQuery, $aRow)
    Switch $RET
        Case $SQLITE_OK
            MsgBox(64, StringFormat("%s -> '%s'", $SQLITE_OK, "SQLITE_OK"), StringFormat(" %-10s  %-10s  %-10s  %-10s ", $aRow[0], $aRow[1], $aRow[2], $aRow[3]))
        Case $SQLITE_DONE
            MsgBox(64, StringFormat("%s -> '%s'", $SQLITE_DONE, "SQLITE_DONE"), "Done, exiting fetch loop.")
            ExitLoop
        Case Else
            MsgBox(16, StringFormat("%s -> '%s'", _SQLite_ErrCode(), _SQLite_ErrMsg()), "Error, exiting fetch loop: " & $RET)
            ExitLoop
    EndSwitch
WEnd

During your fetch loop $SQLITE_OK is returned from the function, and you shouldn't be checking error code. When the fetch hits EOL, you get $SQLITE_DONE returned and SQLITE_OK for error code (not an error). It's also not safe to make those $aRow array references if there was an error because the array may not be valid or have the expected number of elements.

;)


Valuater's AutoIt 1-2-3, Class... Is now in Session!For those who want somebody to write the script for them: RentACoder"Any technology distinguishable from magic is insufficiently advanced." -- Geek's corollary to Clarke's law

Share this post


Link to post
Share on other sites

Hi.

So, it seems that SQLite.dll is not that "idiot proof" than I have believed...

Thanks about the hint, PsaltyDS!


- miXza-81 -

Share this post


Link to post
Share on other sites

So, it seems that SQLite.dll is not that "idiot proof" than I have believed...

Hi,

Don't believe that. SQLite _must_ have a way to indicate common, normal, non-error situations like a query returning an empty rowset, availability of another row for you to fetch, end of rowset, just for talking about result of queries. Now there are other non-fatal situations that may need to take care of, like "base is busy".

All in all, the SQLite interface isn't that dumb.


This wonderful site allows debugging and testing regular expressions (many flavors available). An absolute must have in your bookmarks.
Another excellent RegExp tutorial. Don't forget downloading your copy of up-to-date pcretest.exe and pcregrep.exe here
RegExp tutorial: enough to get started
PCRE v8.33 regexp documentation latest available release and currently implemented in AutoIt beta.

SQLitespeed is another feature-rich premier SQLite manager (includes import/export). Well worth a try.
SQLite Expert (freeware Personal Edition or payware Pro version) is a very useful SQLite database manager.
An excellent eBook covering almost every aspect of SQLite3: a must-read for anyone doing serious work.
SQL tutorial (covers "generic" SQL, but most of it applies to SQLite as well)
A work-in-progress SQLite3 tutorial. Don't miss other LxyzTHW pages!
SQLite official website with full documentation (may be newer than the SQLite library that comes standard with AutoIt)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0