On Fri, Apr 17, 2015 at 12:59 PM, Janke, Julian
wrote:
> Unfortunately, I can't run the shell tool on the es and try the same
> sequence of commands.
>
Why? Don't you have some kind of shell on that embedded system that can run
executables?
According to https://www.sqlite.org/howtocompile.html,
Unfortunately not.
There are no shell on the system to which I have access as an application
developer,
so I don't can run executables.
The only thing I can do is to download c-code applications on a given interface
to the board.
-Original Message-
From: sqlite-users-bounces at mailing
On 17 Apr 2015, at 11:59am, Janke, Julian wrote:
> I've changed the stmt to "SELECT 'Hello World !!';"
> In this case,
>
> sqlite3_step() returns SQLITE_ROW
> sqlite3_column_text() returns 'Hello World !!'
>
> That, looks right.
I agree. And it shows that your C code is working perfectly. F
On 17 Apr 2015, at 11:12am, Janke, Julian wrote:
> I changed my code again:
Move the DROP TABLE command on line 5 to after the _finalize() call. But I
don't think it'll make any difference.
You should not be getting SQLITE_DONE back from your call to _step(). The
documentation says that th
Yes, I downloaded the amalgamation and included it into my project. Since it is
an embedded system with a not out of the box supported operating system, I
wrote my own vfs. Insert, select, delete operations properly work on a database
and as desired.
I've changed the stmt to "SELECT 'Hello Worl
On 4/17/15, Janke, Julian wrote:
> Hello,
> Thanks for your reply.
>
> I changed my code again:
>
> 1) rc = sqlite3_open(dbPath, &db); --> SQLITE_OK
> 2) rc = sqlite3_exec(db, "DROP TABLE IF EXISTS nosuchtable;",
> testCallbackPrint, 0, &zErrMsg);
> 3) rc = sqlite3_prepare_v2(db, "PRAGMA journal_m
Hello,
Thanks for your reply.
I changed my code again:
1) rc = sqlite3_open(dbPath, &db); --> SQLITE_OK
2) rc = sqlite3_exec(db, "DROP TABLE IF EXISTS nosuchtable;",
testCallbackPrint, 0, &zErrMsg);
3) rc = sqlite3_prepare_v2(db, "PRAGMA journal_mode=WAL;", 24, &stmt, NULL);
--> SQLITE_OK
4) rc
Thanks for all the responses. In the end I went with the CREATE TEMP TABLE ...
option which has worked very well and seems to have negligible overhead (on the
order of 0.006s to create ~40 temporary tables and similarly quick to drop
them).
-Original Message-
From: sqlite-users-bounces
8 matches
Mail list logo