On 12/15/17, Edwards, Mark C. wrote:
> sqlite3.c(167291): error C4703: potentially uninitialized local pointer
> variable 'pNode' used
> sqlite3.c(168154): error C4703: potentially uninitialized local pointer
> variable 'pRoot' used
> sqlite3.c(168160): error C4703: potentially uninitialized local
sqlite3.c(167291): error C4703: potentially uninitialized local pointer
variable 'pNode' used
sqlite3.c(168154): error C4703: potentially uninitialized local pointer
variable 'pRoot' used
sqlite3.c(168160): error C4703: potentially uninitialized local pointer
variable 'pChild' used
Two of these
On 12/15/17, Lee, Greg wrote:
> I never got a reply on this issue and someone else tripped up on it:
>
> https://github.com/spack/spack/issues/6698
>
> Any help or even acknowledgement of this message would be appreciated.
>
I believe the problem was fixed on the highlighted check-in here:
https:
I never got a reply on this issue and someone else tripped up on it:
https://github.com/spack/spack/issues/6698
Any help or even acknowledgement of this message would be appreciated.
Thanks,
-Greg
From: Lee, Greg
Sent: Wednesday, May 03, 2017 3:49 PM
To: 'sqlite-users@mailingli
> On Dec 14, 2017, at 11:17 PM, Ajay Gaonkar wrote:
>
> If the above code is fine, then why does the mutex lock initiated at native
> level not getting reflected at Application level?
Your native code opens its own connection to the database. The mutex governs
access to that database _connect
Dear Sqlite Team,
Thanks for looking into this mail.
I am using sqlite database in my Android application with some native code.
The database is shared between Android Application & Native code.
Can you please tell me the ideal behavior in below flow,
In my Android application below native funct
On 15 Dec 2017, at 8:36pm, x wrote:
> I’ll have to look into how to increase the in-memory pager cache.
Before you do anything like that, ask yourself two questions:
a) Is my program actually fast enough without any of these weird picky measures
? Or am I spending lots of time learning deta
Thanks Richard. I take it this is what you’re talking about
“Even though a disk file is allocated for each temporary database, in practice
the temporary database usually resides in the in-memory pager cache and hence
there is very little difference between a pure in-memory database created by
On 12/15/17, x wrote:
>
> Is there any easy way of creating a table that will use mem for speed but
> revert to disc for backup if memory runs out?
>
Make the database filename be an empty string.
--
D. Richard Hipp
d...@sqlite.org
___
sqlite-users ma
Thanks for all the replies. I’ve just finished a test on win32.
Firstly I tried appending a int64_t to a vector until I got an exception. This
happened at i = 60,540,698.
I then created a table in mem with a single integer column and appended
values(2<<62) until I got an exception. This happene
On 12/15/17, x wrote:
> Suppose I execute “attach :memory: as mem” and then create a table in mem
> that requires more space than the available RAM can hold what will happen?
You will get an SQLITE_NOMEM error from SQLite. This is well-tested behavior.
You can run tests yourself by compiling wi
You will get an "Out of Memory" error, since you have run out of V=V memory to
allocate ...
Depending on the vagaries of the OS, all sorts of other hell may break loose as
well, if your "process" out-of-memory condition corresponds to a general OS
out-of-memory condition. That is to say that
> On Dec 15, 2017, at 8:30 AM, x wrote:
>
> Suppose I execute “attach :memory: as mem” and then create a table in mem
> that requires more space than the available RAM can hold what will happen?
On most operating systems, the kernel will use virtual memory, so part of the
table’s address spa
On 15 Dec 2017, at 4:30pm, x wrote:
> Suppose I execute “attach :memory: as mem” and then create a table in mem
> that requires more space than the available RAM can hold what will happen?
The problem would not happen when you create the table. SQLite reserves only a
little space for each t
Try it
create a table and use the zeroblob(n) function to insert lots of blobs of
size n
ie
create table blobs (b blob);
insert into blobs values(zeroblob(1));
insert into blobs values(zeroblob(1));
etc.
interestingly the max blob size is specified as 2147483647 but on my
curre
Suppose I execute “attach :memory: as mem” and then create a table in mem that
requires more space than the available RAM can hold what will happen?
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin
On Fri, Dec 15, 2017 at 7:05 AM, John G wrote:
> If you don't have Tcl/Tk ... if you are using MacOS or Linux you already
> have it.
> On Windows you can download it from https://www.activestate.com/activetcl
>
> I have a religious prohibition against activestate bloatware :)
I found https://www.
If you don't have Tcl/Tk ... if you are using MacOS or Linux you already
have it.
On Windows you can download it from https://www.activestate.com/activetcl
John G
On 14 December 2017 at 12:19, advancenOO
wrote:
> Hello Richard,
>
> I hope to run some tests by myself and I think TCL tests in you
SELECT name, address
CASE behaviour
WHEN 'nice' THEN SELECT toy FROM stocking_stuffers ORDER BY random() LIMIT 1
WHEN 'naughty' THEN 'coal'
ELSE phnglui mgwlnafth cthulhu
END
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
19 matches
Mail list logo
