Thanks all for your responses.
Here is what I have found: If I open a mem DB with sqlite3_open
using NULL as the filename, then use sqlite3_prepare16, the function
fails with "ErrMisuse". But I can use sqlite3_prepare (etc.). But
if I use sqlite3_open with ":memory:" then I can use
sqlite3_prepare16 (etc.) subsequently. So it appears there is some
discrepencies in the core code (I hope this is clear enough).
I would like to see this cleaned up. I think it would be very
clean to be able to specify NULL as the filename and be able to mix
the sqlite3_* and sqlite3_*16 calls.
Quoting Brett Goodman :
And now I find that if I open a mem DB with sqlite3_open then
use
sqlite3_prepare16, the function fails with "ErrMisuse"
Any ideas?
Quoting Brett Goodman :
Hello all. I'm having some trouble with memory DBs. The
documents
that I find on the website say to use ":memory" as the filename
in
the call to sqlite3_open. But the only way I can make the
function
succeed is by passing NULL.
Furthermore, I can't get it work at all if I use sqlite3_open16
(using NULL or ":memory").
Is this a bug or ?
thx
-Brett G.
Quoting Lenster :
Thanks for that info Richard - I will certainly try it for size.
Congratulations on your most prestgious award.
NJH
--
View this message in context:
http://www.nabble.com/Most-appropriate-Web-based-database-%28Newbie%29-t1404628.html#a3794224
Sent from the SQLite forum at Nabble.com.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
