Thanks, Simon.
Simon Slavin-3 wrote
> If possible, you should try to do your synchronisation when your app is
> frontmost only. However, I understand that this may not be appropriate
> for your app.
Exactly, under normal circumstances the synchronization of our app is the
topmost priority, henc
firstly :
Even if I used
#if OS_VXWORKS
|| osAccess(zPath,0) != 0
#endif
or I used
#if OS_VXWORKS
}else if(errno == 0x380003 || errno == 13 )
rc = SQLITE_IOERR_DELETE_NOENT:
#endif
Without the SQLITE_ENABLE_LOCKING_STYLE compile option, I tried the above two
met
On 2 Sep 2014, at 9:50am, Jan Slodicka wrote:
> Simon Slavin-3 wrote
>> If possible, you should try to do your synchronisation when your app is
>> frontmost only. However, I understand that this may not be appropriate
>> for your app.
>
> Exactly, under normal circumstances the synchronization
> -Original Message-
> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
> boun...@sqlite.org] On Behalf Of ???
> Sent: 02 September 2014 13:41
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] HELP sqlite3 used in vxworks has some problem
>
>
>
> firstly :
>
Thank Andy Ling. best wishes.
regards
Wang Qinggang.
At 2014-09-02 09:45:47, "Andy Ling" wrote:
>> -Original Message-
>> From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users-
>> boun...@sqlite.org] On Behalf Of ???
>> Sent: 02 September 2014 13:41
>> To: General Discus
On 29/08/14 12:55, Bob Moran wrote:
> The return code (rc) is SQLITE_OK, but "stmnt" is NULL (0)
>
> if I start the application and wait for at least 1 minute, everything works.
You get NULL back from prepare with SQLITE_OK if the statement doesn't do
anything. Examples are empty strings or comm
Greetings!
I know that SQLite dates are of the form -MM-DD and I like that. :-) I
want to find out why these are working.
create table t (a date, val integer);
insert into t values ('2010-01-01', 10);
insert into t values ('2010-1-1', 10);
insert into t values ('2010-1-01', 10);
insert i
On Sep 2, 2014, at 9:48 PM, jose isaias cabrera wrote:
> Thoughts? Thanks.
SQLite doesn’t have date per se. You are free to store dates as either text or
number, or anything you please. But it’s your responsibility to keep it
straight.
___
sqlite-
On Tue, Sep 2, 2014 at 3:48 PM, jose isaias cabrera wrote:
>
> Greetings!
>
> I know that SQLite dates are of the form -MM-DD and I like that. :-)
> I want to find out why these are working.
>
SQLite does not have a special "date" type. SQLite stores dates as either
strings, or integers, or
"Richard Hipp" wrote...
On Tue, Sep 2, 2014 at 3:48 PM, jose isaias cabrera
wrote:
Greetings!
I know that SQLite dates are of the form -MM-DD and I like that. :-)
I want to find out why these are working.
SQLite does not have a special "date" type. SQLite stores dates as either
st
"Petite Abeille" wrote...
On Sep 2, 2014, at 9:48 PM, jose isaias cabrera
wrote:
Thoughts? Thanks.
SQLite doesn’t have date per se. You are free to store dates as either
text or number, or anything you please. But it’s your responsibility to
keep it straight.
thanks.
___
Found more of what the issue is. I noticed that my SQL text was being
overwritten on the return from the call to prepare_v2.
Stepping through the SQlite3 code I discovered that a malloc call for 500+
bytes was returning a pointer 8 bytes below my SQL string.
Don't have the foggiest notion as to w
> On 3 Sep 2014, at 5:24am, Bob Moran wrote:
>
> Found more of what the issue is. I noticed that my SQL text was being
> overwritten on the return from the call to prepare_v2.
> Stepping through the SQlite3 code I discovered that a malloc call for 500+
> bytes was returning a pointer 8 bytes b
13 matches
Mail list logo
