On 4/21/05, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> How about sqlite3_transfer_bindings(). So if you get an
> SQLITE_SCHEMA error you rerun sqlite3_prepare() to get
> a new sqlite3_stmt, then call sqlite3_transfer_bindings()
> to transfer bindings from the old statement over to the
> new
On Thu, 2005-04-21 at 18:18 -0700, Vladimir Vukicevic wrote:
> On 4/21/05, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> > So when the schema changes, it is not a matter of changes
> > a few bits and pieces of the VM. The VM must be completely
> > reconstructed. Its a complete do-over.
>
> Yep,
On 4/21/05, D. Richard Hipp <[EMAIL PROTECTED]> wrote:
> So when the schema changes, it is not a matter of changes
> a few bits and pieces of the VM. The VM must be completely
> reconstructed. Its a complete do-over.
Yep, I guess what I'm suggesting is just doing that reconstruction
internally
On Thu, 2005-04-21 at 14:10 -0700, Vladimir Vukicevic wrote:
> Is there any reason that step() can't recreate the
> bits of the VDBE that need to be updated itself in case of a
> SQLITE_SCHEMA error, while preserving current parameter bindings?
>
You make it sound as if only a few parameters in
(Sorry, accidentally dropped the sqlite mailing list from my first reply)
You're misunderstanding. The only "schema change" is creating
additional tables, that are not referenced by any existing statements.
There are many reasons why one might want to do this. However,
currently, doing so
I've been using sqlite for several months now and have never had a SQLITE_SCHEMA
error. What are you doing that's causing it?
On 4/21/05, Vladimir Vukicevic <[EMAIL PROTECTED]> wrote:
> Right now it's quite difficult to implement any kind of higher-level
> wrapper over
Right now it's quite difficult to implement any kind of higher-level
wrapper over sqlite3_prepare()/sqlite3_step()/etc., because of the
semantics of the SQLITE_SCHEMA error. If you bind values to
parameters of a sqlite3_stmt, you have to redo that binding after you
recreate the sqlite3_stmt due
On Thu, Apr 21, 2005 at 11:57:19AM -0700, Darren Duncan wrote:
> One of your problems is that you are using single quotes for a delimited
> identifier, "Open|SpeedShop", when you should be using double quotes.
>
> Single quotes means a string literal in the SQL standard, where double quotes
> a
Hello,
This is my first post to this mailing list. While reading through
the Sqlite Wiki I came across an interesting function at
'http://web.utk.edu/~jplyon/sqlite/code/freepages.c' for counting the
number of free pages in a database by James P. Lyon. I wanted to use
this code in
At 12:07 PM -0500 4/21/05, William Hachfeld wrote:
sqlite> CREATE TABLE 'Open|SpeedShop' (version INTEGER);
sqlite> INSERT INTO 'Open|SpeedShop' (version) VALUES (1);
One of your problems is that you are using single quotes for a
delimited identifier, "Open|SpeedShop", when you should be using
On Thu, 2005-04-21 at 12:07 -0500, William Hachfeld wrote:
> Heh everyone!
>
> I've recently tried to upgrade from SQLite 3.0.8 to 3.2.1 and have run into a
> snag. This is probably something REAL simple that I'm just not seeing. I'm
> hoping someone can point out my stupid mistake...
>
COLUMN
Quite right Thomas and Jolan! I knew it was going to be something stupid on my
part. If I change the field "column" to "clumn" it works just fine.
Thanks!
-- William Hachfeld
On Thu, Apr 21, 2005 at 12:07:24PM -0500, William Hachfeld wrote:
> I've recently tried to upgrade from SQLite 3.0.8 to 3.2.1 and have run into a
> snag. This is probably something REAL simple that I'm just not seeing. I'm
> hoping someone can point out my stupid mistake...
>
> When I rebuild our
I'd guess that "column" is now a reserved word - probably because of
the addition of ALTER TABLE. I have no proof that back that up though.
:)
-Tom
> -Original Message-
> From: William Hachfeld [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 21, 2005 1:07 PM
> To:
Heh everyone!
I've recently tried to upgrade from SQLite 3.0.8 to 3.2.1 and have run into a
snag. This is probably something REAL simple that I'm just not seeing. I'm
hoping someone can point out my stupid mistake...
When I rebuild our project with 3.2.1 instead of 3.0.8, I'm getting a syntax
On Thu, Apr 21, 2005 at 11:49:21AM +0100, Christian Smith wrote:
> I know the snippet above is from a test program, but don't ever put things
> like sqlite3_exec() inside an assert()! I hope you're (OP) not doing this in
> your application.
I realize that evaluation of assert() is short-circuited
> I do not unfortunately have any place to host this work. There may be
> somebody on this list who knows of a place where this can be published
> for any members who may with make use of it.
>
http://www.sqlite.org/contrib
--
D. Richard Hipp <[EMAIL PROTECTED]>
Ben Clewett wrote:
I do not unfortunately have any place to host this work. There may be
somebody on this list who knows of a place where this can be published
for any members who may with make use of it.
http://sourceforge.net/ ?
On Wed, 20 Apr 2005, Klint Gore wrote:
>On Tue, 19 Apr 2005 12:40:51 -0500, William Hachfeld <[EMAIL PROTECTED]> wrote:
>> uint64_t t_stop = Now();
>>
>> assert(sqlite3_exec(handle, "COMMIT TRANSACTION;",
>> NULL, NULL, NULL) == SQLITE_OK);
>
>What happens to your
On Wed, 20 Apr 2005, Ted Unangst wrote:
>Christian Smith wrote:
>> On Mon, 18 Apr 2005, Cem Vedat ISIK wrote:
>>
>>
>>>Having a lot of cross compiling trials and errors, I have decided not to
>>>cross compile, but to compile the SQLite on Motorola PowerPC itself.
>>
>>
>>
>> If this is still the
Dear users,
I have attached another version of my wrapper for SQLite.
This returns a table in memory and releases all locks. Therefore
providing a safer, simpler and very useful API.
This version uses less memory, gets meta-data and fixes a bug or two.
This version also provides some streaming
You could see document that see C file Cfunction.
URL:http://www.sqlite.org/capi3.html
under macro define
{
#define SQLITE_OK 0 /* Successful result */
#define SQLITE_ERROR1 /* SQL error or missing database */
#define SQLITE_INTERNAL 2 /* An internal logic error in
22 matches
Mail list logo
