On Wed, Oct 23, 2013 at 8:33 PM, David Simmons <[email protected]>wrote:
> The paths we follow are sometimes clouded with ego that prevent seeing the > obvious. Making code changes to first find and then include an explicit > path to the sqlite database solved the problem. Thanks for your help I can > now move forward. > > BTW - I could not isolated Error Code 255 to a specific cause - sort of a > general "Failure Code". > i suspect the error code you are referring to is the one coming back from the shell (via the python interpreter), not from sqlite3. A quick scan of sqlite3.h doesn't reveal 255 as an error code (though there are some codes created via bitshifts which i did not bother trying to decode). In that case, there is no way to track it back except to read the docs for the tool causing the error (in this case python). In my experience, 255 is often associated with a segfault, but that's certainly not a law. The golden rule is: check the result code of all operations where they happen, not at the end of the program. If any op fails, all other downstream results are undefined and their error codes will only confuse the matter. That said, i have no idea how the python sqlite API reports errors - maybe it's throwing an exception, which causes python to abort with code 255, but i'm just speculating. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
