On Thu, Oct 23, 2014 at 4:03 PM, Tomislav Ljubej wrote:
> I've searched Banshee's source code and it seems 'CoreCache' is a TEMP
> table according to some comments in the code but I have no clue where
> it's actually defined, there is no 'CREATE TABLE' statement in the
> code
On Thu, Oct 16, 2014 at 4:33 PM, k wrote:
> Hi all,
> this is my first reply-to post to this mailing list (using gmane nttp
> interface) so I hope this post passes moderation ok and is correctly
> threaded and not duplicated...).
>
> Regarding the inability to use
I've searched Banshee's source code and it seems 'CoreCache' is a TEMP
table according to some comments in the code but I have no clue where
it's actually defined, there is no 'CREATE TABLE' statement in the
code for that particular table (I've searched even with TEMP or
TEMPORARY keywords,
On Thu, Oct 23, 2014 at 2:25 PM, Dennis Field wrote:
>
>
> Are there any omit/other preprocessor defines that are particularly helpful
> for reducing memory usage?
>
>
SQLITE_SMALL_STACK - but that will require regenerating the amalgamation.
--
D. Richard Hipp
Thanks, all! Sorry for the delayed response. I ran into an SD card reading
issue that I'm still trying to solve (multiple block reading), and I've
worked around it for now to keep trying to make progress on the database.
I have switched to memsys3 and the 60 KB heap seems sufficient for now to
On Thu, Oct 23, 2014 at 11:55 AM, Luigi Iemma wrote:
> Hi,
>
> SELECT TdoIdoc,RdoCart,RdoQuat
> FROM Tesdoc
> INNER JOIN Rigdoc ON RdoIdoc BETWEEN TdoIdoc*1000 AND
> TdoIdoc*1000+999
> WHERE TdoTipo=60 AND TdoAnno BETWEEN 2014 AND 2014
> GROUP BY TdoIdoc
>
>
On 23 Oct 2014, at 4:55pm, Luigi Iemma wrote:
> When I run this query on 3.8.5 it takes 0.126 seconds,
> when I run this query on 3.8.7 it takes 17.37 seconds
Can you do an ANALYZE then try it again ?
Simon.
___
sqlite-users
Hi,
SELECT TdoIdoc,RdoCart,RdoQuat
FROM Tesdoc
INNER JOIN Rigdoc ON RdoIdoc BETWEEN TdoIdoc*1000 AND
TdoIdoc*1000+999
WHERE TdoTipo=60 AND TdoAnno BETWEEN 2014 AND 2014
GROUP BY TdoIdoc
When I run this query on 3.8.5 it takes 0.126 seconds,
when I run this query on 3.8.7 it takes
On Thu, Oct 23, 2014 at 2:47 PM, dd wrote:
> Hi,
>
> database schema defined with collate nocase. It supports only for ascii
> (upper and lower). If I want to support db for other characters with
> nocase, what steps I need to consider during schema design.
>
> for ex:
>
Dear Richard, Ralf
From: Richard Hipp
Sent: Wed, 22 Oct 2014 21:53:36 -0400
To: General Discussion of SQLite Database Cc: Ralf
Mardorf
Subject: Re: [sqlite] [regression] SQLite
supermariobros wrote:
> If I am using FTQ that looks like this
> SELECT * FROM mail WHERE body MATCH 'sqlite'
> can I add to it "WHERE rowid > 5 AND rwoid <10"
> or it will significantly slow it down.
How much did it slow down when you tested it?
Anyway,
without index:
sqlite> EXPLAIN
http://www.sqlite.org/c3ref/clear_bindings.html
-Ursprüngliche Nachricht-
Von: Baruch Burstein [mailto:bmburst...@gmail.com]
Gesendet: Donnerstag, 23. Oktober 2014 13:47
An: General Discussion of SQLite Database
Betreff: [sqlite] Unbinding parameters
It says here
Sorry for the noise, but I found it:
https://www.sqlite.org/c3ref/clear_bindings.html
On Thu, Oct 23, 2014 at 2:46 PM, Baruch Burstein
wrote:
> It says here (https://www.sqlite.org/c3ref/bind_blob.html) that
> a) Unbound parameters are interpreted as NULL, and
> b)
Hi,
database schema defined with collate nocase. It supports only for ascii
(upper and lower). If I want to support db for other characters with
nocase, what steps I need to consider during schema design.
for ex:
*À Á Â Ã Ä Å Æ = *
* à á â ã ä å æ *
Thanks.
It says here (https://www.sqlite.org/c3ref/bind_blob.html) that
a) Unbound parameters are interpreted as NULL, and
b) Bindings are not cleared by sqlite3_reset()
Is there any way to clear all bindings, so that if I don't set them again
they will insert NULL?
--
˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ
Hi,
I have an app written in Android/Xamarin.
Database [SQLite version 3.7.4] is using custom collation sequence.
Collation sequence is loaded into DB on app startup.
// as described here:
http://www.codeproject.com/Articles/44349/Case-Insensitive-Sort-of-UTF-Data-Using-System-Da
Now when I try
Quick question. If I am using FTQ that looks like this "SELECT * FROM mail
WHERE body MATCH 'sqlite' " can I add to it "WHERE rowid > 5 AND rwoid <10"
or it will significantly slow it down. If so what would be the best
approach for pagination, For example if I get 500 rows with the matching
term
Or maybe, if I am using android, it should be done at the cursor level?
--
View this message in context:
http://sqlite.1065341.n5.nabble.com/FTS-pagination-tp78754p78755.html
Sent from the SQLite mailing list archive at Nabble.com.
___
sqlite-users
18 matches
Mail list logo