Yes, I can see that SQLite is doing just small allocations using memory
methods.
I also tried to limit the size of database using following two methods
rc = sqlite3_config(SQLITE_CONFIG_HEAP, buffer, 500, 64);
if(rc != SQLITE_OK)
{
printf("Failed to set custom heap memory
On 7/13/18, Martin Vystrčil wrote:
>
> But still, I would like to solve this somehow, could you please suggest me
> some point, where to start ? Are there any possible compilation options, to
> limit this allocation ?
It is not SQLite that is doing this allocation. I suspect it is
something happ
Thank you both for help.
What Richar Hipp wrote is truth and something what I also saw using
valgrind - memory allocation (overall consumption) of around 300 - 500 kB.
To answer at least some one Bob's question from first e-mail, I'm trying to
open in memory database (:memory:), so size of databas
On Jul 13, 2018, at 10:15 AM, dmp wrote:
>
> Seems .dump uses a short output of skipping the column names.
To call that a problem requires that you justify why you’d need the column
names to be specified in the INSERT statements.
If you take the .dump file as-given and just run it, the INSERT
On 07/07/18 19:47, E.Pasma wrote:
But the ideas allow a parameter name to be identical to a column name,
which must be an error.
While I might prefer that to be the case, it's actually not. We do not
have the ability for column expressions to reference other columns, so
there is no ambiguity
I'm sorry, but I don't see a question in your post.
Are you suggesting that the SQLite command-line tool has a bug ?
Are you suggesting that Ajqvue has a bug ?
Simon.
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglist
Hello,
Recently in testing my GUI tool I made a comparison from the
tool's dump and SQLite's command line .dump tool.
Seems .dump uses a short output of skipping the column names.
According to some of my research for various databases I use
one of these as options for SQL dump output:
http://ajq
On 7/12/18, danap wrote:
>> I use a dump
>> in my interface which I used with diff to compare changes in my
>> personal expense database. This was to insure changes introduced in work
>> on the interface were not screwing things up. Very helpful to insure
>> your not introducing bugs.
D. Richard H
On Fri, 13 Jul 2018, Richard Hipp wrote:
The OP's test program (with a bug fix, various whitespace changes, and
the addition of a call to sqlite3_memory_used()) is show below.
sqlite3_memory_used() reports no difference in memory allocation.
The usage is uninitialized/unmodified virtual memory
On 7/13/18, Bob Friesenhahn wrote:
> On Fri, 13 Jul 2018, Martin Vystrčil wrote:
>
>> Hello everyone,
>>
>> I have a problem using sqlite in one of my project. When I create instance
>> of sqlite (sqlite_open) from main thread, memory consumption is in normal
>> (a few megabytes). But when I start
People double clicking .csv's to edit them in Excel has caused so many
headaches.
Leading 0's dropped, things like "4E3" turned into 4000, "3-12" turned into
"12-Mar", mixups between Windows encoding and UTF-8 mangling characters, etc.
If you have to or prefer to view things in Excel, the way I
On Fri, 13 Jul 2018, Martin Vystrčil wrote:
Hello everyone,
I have a problem using sqlite in one of my project. When I create instance
of sqlite (sqlite_open) from main thread, memory consumption is in normal
(a few megabytes). But when I start sqlite from another thread, immediately
around 70
Hello everyone,
I have a problem using sqlite in one of my project. When I create instance
of sqlite (sqlite_open) from main thread, memory consumption is in normal
(a few megabytes). But when I start sqlite from another thread, immediately
around 70 - 80 MB of memory is allocated.
Here is the sm
13 matches
Mail list logo