> If your build is frequently trying to unlink a file that does not exist,
> then something is wrong. We need to figure out what that is and fix it.
I have added some debug.
First I create a brand new database called /ata0:3/testdb.sql
Then I try and create a table and get an error from
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of Andy Ling
> Sent: 13 August 2014 10:06
> To: 'Richard Hipp'
> Cc: General Discussion of SQLite Database
> Subject: Re: [sqlite] HELP sqlite3 used in vxworks has
When I add sqlite3.c and sqlite3.h to xcode ios cocoa project, and compiled,
the error msg is:
Sqlite3 class is not a objective class, who have any cocoa sqlite source, I
don't know how to do.
___
sqlite-users mailing list
sqlite-users@sqlite.org
OK, I did find some cases where unlink() is called on files that do not
exist. We must have added those within the past couple of years
Anyway, a patch has now been checked in.
On Wed, Aug 13, 2014 at 5:09 AM, Andy Ling wrote:
>
>
> > -Original Message-
> >
Thanks for the advice everyone, I'd not considered the group by clause here.
The following seems to work so far:
SELECT items.id,
items.prod_code,
items.creation_date,
collections.book_in_date as last_book_in_date,
collections.collection_date as last_collection_date
Hi,
I stumbled upon a bug in my code which looked like a wrong sqlite behavior.
When simply using the "begin - pragma journal_mode=wal - commit" query
sequence, sqlite return a proper error saying this is not allowed.
However if I execute a command affecting the database structure (such as
There's a class of errors that affect lots of programs, where
backup and/or antivirus software have a file open "unexpectedly",
which causes routine operations such as delete and rename to
fail unexpectedly.
I once promoted a fix for sqlite that combatted these problems
by retrying such
There's a class of errors that affect lots of programs, where
backup and/or antivirus software have a file open "unexpectedly",
which causes routine operations such as delete and rename to
fail unexpectedly.
I once promoted a fix for sqlite that combatted these problems
by retrying such
On Tue, Aug 12, 2014 at 12:35 PM, Jean GIARD wrote:
>
> I know it's not a good behavior to have structure queries inside a
> transaction ...
>
There is absolutely nothing wrong with doing DDL statements inside a
transaction in SQLite. Other SQL database engines might have
> From: drhsql...@gmail.com [mailto:drhsql...@gmail.com] On Behalf Of Richard
> Hipp
> Sent: 13 August 2014 12:40
> To: Andy Ling
> Cc: General Discussion of SQLite Database
> Subject: Re: [sqlite] HELP sqlite3 used in vxworks has someproblem?
> OK, I did find some cases where unlink() is
Alright, thank you for these precisions.
On 08/13/2014 02:28 PM, Richard Hipp wrote:
On Tue, Aug 12, 2014 at 12:35 PM, Jean GIARD wrote:
I know it's not a good behavior to have structure queries inside a
transaction ...
There is absolutely nothing wrong with doing DDL
Dear list members,
I'm trying to extract the results of a query that returns fairly large amounts
of data (100-200Mb) as quickly as possible using the c/c++ api.
Is there any way to avoid unnecessarily duplicating the data coming from the
following functions?
const unsigned char
On 13/08/14 06:25, Nathaniel Trellice wrote:
> Is there any way to avoid unnecessarily duplicating the data coming from the
> following functions?
You will need to duplicate. You can use the memory allocation/copying
scheme of your choice. I'm rather fond of the hierarchical/pool based ones
On Wed, Aug 13, 2014 at 9:25 AM, Nathaniel Trellice
wrote:
> Dear list members,
>
> I'm trying to extract the results of a query that returns fairly large
> amounts of data (100-200Mb) as quickly as possible using the c/c++ api.
>
> Is there any way to avoid unnecessarily
On 13/08/14 02:31, YAN HONG YE wrote:
> When I add sqlite3.c and sqlite3.h to xcode ios cocoa project, and compiled,
> the error msg is:
> Sqlite3 class is not a objective class, who have any cocoa sqlite source, I
> don't know how to do.
iOS already includes SQLite as a shared library.
On Aug 13, 2014, at 3:43 AM, Keith Medcalf wrote:
> I don't think you want max() around collections.book_in_date. You want the
> max(collection_date) but the book_in_date from that row. Since the
> collection_date is unique, the book_in_date can only come from one
On Aug 13, 2014, at 2:31 AM, YAN HONG YE wrote:
> When I add sqlite3.c and sqlite3.h to xcode ios cocoa project, and compiled,
> the error msg is:
> Sqlite3 class is not a objective class, who have any cocoa sqlite source, I
> don't know how to do.
If you compile in a
17 matches
Mail list logo