Igor Tandetnik wrote:
eternelmangekyosharingan
eternelmangekyosharin...@gmail.com
wrote:
I create the following table:
sqlite create table t1(a);
sqlite insert into t1 values(123456789.123456789);
I ran the following commands:
sqlite select * from t1;
123456789.123457
sqlite
On 2/24/10 19:12 , Mike Shal mar...@gmail.com wrote:
On 2/24/10, Jean-Denis Muys jdm...@kleegroup.com wrote:
On 2/24/10 9:36 , Simon Davies simon.james.dav...@googlemail.com wrote:
Rogue semicolon on line
if( sqlite3_close( db ) != SQLITE_OK );
Regards,
Simon
I have been
On 2/24/10 19:19 , D. Richard Hipp d...@hwaci.com wrote:
On Feb 24, 2010, at 1:12 PM, Mike Shal wrote:
This compiler is llvm. Check it out at http://llvm.org
You can test for this mistake on the demo page at http://llvm.org/
demo
FWIW, there are currently two places in SQLite
On Wed, Feb 24, 2010 at 5:54 PM, eternelmangekyosharingan
eternelmangekyosharin...@gmail.com wrote:
I'm sorry but I don't get your answer.
Can you provide further explanations, please ?
Well, it is entirely possible that I have not understood your
question, and from Igor and Dan's answers, it
We are using sqlite in a low memory environment and as such have been using
the MEMSYS5 memory allocator. This has been working great to confine our
memory usage to the buffer that gets passed during start time. I have
recently run into some strange results while doing a step to insert a blob
into
Hi,
I thought that prepared statements in non-finalized state isn't compatible
with locking mechanism in db sharing environment i.e. if I want for any of
several processes not to hang waiting for EXCLUSIVE lock none of others
should use non-finalized prepared statements. But today I found that
Could it be because of fragmentation issues? When you allow more cache
pages to be allocated you allow more fragmentation to be introduced.
And although in total there could be enough memory available there
could still be no solid block of sufficient size available.
From the comment in mem5.c:
So is such behavior documented and can be used or should I still avoid
keeping such live statements in db-shared enviroment?
It's documented that sqlite3_finalize AND sqlite3_reset release all
locks acquired by the statement. So after resetting the statement you
can keep it as long as you want,
On Feb 25, 2010, at 10:19 AM, Rob Read wrote:
We are using sqlite in a low memory environment and as such have
been using
the MEMSYS5 memory allocator. This has been working great to confine
our
memory usage to the buffer that gets passed during start time. I have
recently run into
How can I get User name and password to login to Wiki?
Steve Topov
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
On Feb 25, 2010, at 3:29 PM, Steve Topov wrote:
How can I get User name and password to login to Wiki?
We don't have a open wiki right now.
The old CVSTrac wiki at http://www.sqlite.org/cvstrac/wiki is no
longer monitored and was starting to pick up spam, so I turned off
write permission
I wanted to update information about our products SQLPro -
http://www.vive.net/products/sqlpro.htm and DataPro -
http://www.vive.net/products/datapro.htm in ManagementTools and
ConverterTools.
Steve Topov
Vive Corp.
-Original Message-
From: sqlite-users-boun...@sqlite.org
On Feb 25, 2010, at 4:08 PM, Steve Topov wrote:
I wanted to update information about our products SQLPro -
http://www.vive.net/products/sqlpro.htm and DataPro -
http://www.vive.net/products/datapro.htm in ManagementTools and
ConverterTools.
Fair enough. I've reenable access to the CVSTrac
I have found the following:
BEGIN; UPDATE entry SET Spinnaker=No ,Singlehand=Doublehand
,Doublehand=Third ,Multi=Multihull ,Furler= WHERE ROWID=45; COMMIT
Results in the value of the column Singlehand to be set to the current value on
the column Doublehand for this ROWID.
Experiment show
Ray Irvine c34irvine1...@comcast.net
wrote:
I have found the following:
BEGIN; UPDATE entry SET Spinnaker=No ,Singlehand=Doublehand
,Doublehand=Third ,Multi=Multihull ,Furler= WHERE ROWID=45;
COMMIT
In SQL, string literals should be enclosed in single quotes. Column and table
names
Shane Harrelson sh...@... writes:
...
I suspect that one of these quirks in your build environment is being
exposed by the code in winCurrentTime().Perhaps you could debug through
the code and find where the calculations are going wrong? In this way we
could provide more help.
16 matches
Mail list logo
