On Fri, Jul 12, 2013 at 3:58 AM, Elan Feingold wrote:
> Just to update, we're attempting to move to a 3.8.0 snapshot, and we've
> run into another possibly pathological case you might want to be aware of
> (same schema).
>
Please try again with the latest snapshot:
Bernd Lehmkuhl wrote:
>
> The actual table definition is :
> CREATE TABLE T_VWG_ABFALLVERZEICHNIS (SCHLUESSEL String, BESCHREIBUNG
String, BEMERKUNG String, ID_GUID String,
> IST_PAUSCHALIERT String, IST_KATEGORIE_ESK_BETRIEBSSTOF String);
>
> SQLite version 3.7.16.2 2013-04-12 11:52:43
> Enter
On Tue, 16 Jul 2013 18:17:41 +0200
Paolo Bolzoni wrote:
> I tried the experiment again with -g3 -O0, I got less
> information than expected (there are still many unknown
> symbols in libsqlite3.so), but the function requiring all
> this memory is sqlite3_step.
Can
On 7/16/2013 12:54 PM, Riccardo Vianello wrote:
according to the documentation for sqlite3_get_auxdata and
sqlite3_set_auxdata "[...] metadata is preserved between function
calls for expressions that are constant at compile time. This includes
literal values and parameters.".
Does the binding
On 16 Jul 2013, at 5:17pm, Paolo Bolzoni wrote:
> the function requiring all
> this memory is sqlite3_step.
>
> So maybe it is one complex query?
Possibly a query for which no good index exists, so SQLite decides to make up
its own temporary index.
If you
Hi all,
according to the documentation for sqlite3_get_auxdata and
sqlite3_set_auxdata "[...] metadata is preserved between function
calls for expressions that are constant at compile time. This includes
literal values and parameters.".
Does the binding of values affect the lifetime of the
I tried the experiment again with -g3 -O0, I got less
information than expected (there are still many unknown
symbols in libsqlite3.so), but the function requiring all
this memory is sqlite3_step.
So maybe it is one complex query?
I would like to avoid excessive swapping on the
production server,
Hey folks,
the problem still exists (or rather again). Shortly after my initial
email someone decided to turn the redirect to HTTPS off again, but now
it's back, only the certificate chain hasn't been fixed.
OpenSSL gives me:
$ openssl s_client -connect www.sqlite.org:443
CONNECTED(0003)
Here at the SQLite.org office, we frequently get phone calls from people
who are trying to recover chat logs or contacts or other information stored
in SQLite databases on iPhones and Android and other smartphones. This
being outside our area of expertise, we are unable to help.
But maybe some
On 16 Jul 2013, at 12:26pm, Bernd Lehmkuhl wrote:
> The actual table definition is :
> CREATE TABLE T_VWG_ABFALLVERZEICHNIS (SCHLUESSEL String, BESCHREIBUNG String,
> BEMERKUNG String, ID_GUID String, IST_PAUSCHALIERT String,
> IST_KATEGORIE_ESK_BETRIEBSSTOF String);
On Fri, Jul 12, 2013 at 3:58 AM, Elan Feingold wrote:
> Just to update, we're attempting to move to a 3.8.0 snapshot, and we've
> run into another possibly pathological case you might want to be aware of
> (same schema). The query is...
>
Thanks for the follow-up report. The
Hello Nickye,
I insert strings with "." all the time. In fact I'd say most
insertions I do have "."s in them so, I don't think there's an
inherent problem in Sqlite. I convert everything to UTF8 before I
insert though the UTF8 of "." is ".".
C
Monday, July 15, 2013,
On 7/15/2013 3:13 PM, nic...@mail.ru wrote:
Prepared statement SQL: "INSERT INTO tbl VALUES(?1);"
Column type:TEXT
String to bind (ASCII, zero terminated): "abcd.ef"
nBytes parameter: -1
destructor parameter: SQLITE_STATIC
Result after call sqlite3_step: "abcd"
Works for me. There's must be
This is documented, I think.
Based on 2.1 (bullet 5) of http://www.sqlite.org/datatype3.html the default
affinity is numeric. Since STRING is not understood, it has numeric
affinity.
-Original Message-
The actual table definition is :
CREATE TABLE T_VWG_ABFALLVERZEICHNIS
> On 16 Jul 2013, at 4:39am, Bernd Lehmkuhl wrote:
>
>> Am 15.07.2013 22:26, schrieb Simon Slavin:
>>>
>>> The following two statements do different things.
>>>
>>> INSERT INTO myTable VALUES (01)
>>> INSERT INTO myTable VALUES ('01')
>>>
>>> Can you tell what's being done in your
Hello,
Prepared statement SQL: "INSERT INTO tbl VALUES(?1);"
Column type:TEXT
String to bind (ASCII, zero terminated): "abcd.ef"
nBytes parameter: -1
destructor parameter: SQLITE_STATIC
Result after call sqlite3_step: "abcd"
With nBytes==(len(String)) there's no problem,
On Tue, Jul 16, 2013 at 1:00 PM, Dan Kennedy wrote:
> On 07/16/2013 01:49 AM, Paolo Bolzoni wrote:
> A very large blob or string result?
I would exclude this, I do use blobs... but they are at most
few dozen of bytes...
> Code allocates (or leaks)
> tremendous numbers of
On 07/16/2013 01:49 AM, Paolo Bolzoni wrote:
From 35-40MB to 940MB; I would put massif result but I think the
list deletes attachments.
A very large blob or string result? Code allocates (or leaks)
tremendous numbers of sqlite3_stmt* handles?
SQLite has various APIs for querying memory
On 16 Jul 2013, at 4:39am, Bernd Lehmkuhl wrote:
> Am 15.07.2013 22:26, schrieb Simon Slavin:
>>
>> The following two statements do different things.
>>
>> INSERT INTO myTable VALUES (01)
>> INSERT INTO myTable VALUES ('01')
>>
>> Can you tell what's being done in your setup ?
The test ended sometime during the night and setting temp_store to 0
the result is exactly the same. I suspect it was the default anyway.
On Mon, Jul 15, 2013 at 9:20 PM, Paolo Bolzoni
wrote:
> On Mon, Jul 15, 2013 at 9:08 PM, Eduardo Morras
20 matches
Mail list logo