Jay Sprenkle wrote:
> On 1/24/07, Jef Driesen <[EMAIL PROTECTED]> wrote:
>>
>> Do I need to use sqlite3_close if the call to sqlite3_open indicated an
>> error? The documentation for sqlite3_open says "An sqlite3* handle is
>> returned in *ppDb, even if an error occurs." So I assumed the answer is
[EMAIL PROTECTED] wrote:
"Jef Driesen" <[EMAIL PROTECTED]> wrote:
I did. sqlite3_close is called automatically for SQLITE_NOMEM, but not for
other cases. So I guess sqlite3_close is still needed. But then it
shouldn't return an error, or am I wrong?
I don't think any error other than
Jay Sprenkle wrote:
On 1/24/07, Jef Driesen <[EMAIL PROTECTED]> wrote:
Do I need to use sqlite3_close if the call to sqlite3_open indicated an
error? The documentation for sqlite3_open says "An sqlite3* handle is
returned in *ppDb, even if an error occurs." So I assumed the answer is
yes.
I
On 1/24/07, Jef Driesen <[EMAIL PROTECTED]> wrote:
Do I need to use sqlite3_close if the call to sqlite3_open indicated an
error? The documentation for sqlite3_open says "An sqlite3* handle is
returned in *ppDb, even if an error occurs." So I assumed the answer is
yes.
I never do, since if
Do I need to use sqlite3_close if the call to sqlite3_open indicated an
error? The documentation for sqlite3_open says "An sqlite3* handle is
returned in *ppDb, even if an error occurs." So I assumed the answer is yes.
But if I try this code (on a non-existing file and no write permissions):
5 matches
Mail list logo