On Mon, Oct 20, 2014 at 5:21 PM, Dennis Field wrote:
>
> When I initialize SQLite, I am instructing it to take a single heap for
> memsys5 of 60 * 1024.
>
Have you tried using memsys3 instead of memsys5? Memsys3 can be more
memory-efficient.
You might also want to disable
I have no idea what is 100% required in the database, but I THINK you can
include some compiler directives that REMOVE certain features. I know FTS
is an optional thing, but I don't know if it is included as part of the
default build or not. CTE (I think that is it?) might also be something
you
One possibility might be to use the long-obsolete SQLite2, which was
around when PC's had much smaller memories.
I know it is heresy to suggest it, and you would have a lot of recoding
to do, but it seems that it might be workable.
Gerry Snyder
I have SQLite compiled for a Cortex M4 with 256 KB of RAM. Currently, as
other things on the system are taking up a grand total of about 190 KB, I'm
able to allocate about 60KB to SQLite and I'm running out of memory just
trying to select a 16-byte blob and a string from a pair of tables.
SQL log
On 10/18/2014 05:45 AM, Deon Brewis wrote:
I'm trying to follow Richard's advise to work around this issue, which is:
"Is that database ever used by more than a single process. (Use by multiple
threads using separate connections does not count - I mean really used by
multiple processes with
5 matches
Mail list logo