SongbookDB wrote:
I'd now like to order the Language = rows by another column, Artist,
but cannot crack how to restructure the query to accommodate this.
SELECT * FROM
(SELECT *
FROM table1
WHERE Language != COLLATE NOCASE
ORDER BY Language COLLATE NOCASE)
UNION ALL
SELECT *
FROM
On 3 Nov 2013, at 9:07am, Dominique Devienne ddevie...@gmail.com wrote:
This is consistent with findings we've seen in our own software, where
rewriting queries to use joins instead of custom SQL functions sped up some
queries considerably.
The SQLite engine completely understands JOINs. It
On 3 Nov 2013, at 3:24am, SongbookDB shaun_thom...@songbookdb.com wrote:
WHERE Language != COLLATE NOCASE
ORDER BY Language COLLATE NOCASE)
By the way, if every time you refer to your Language column you want it colated
NOCASE, it's far more efficient to do it when you define the column in
Hi,
I have been using SQLite for one project of mine and I will be storing TBs
of Data.
Now there will be a lot of selections in this database and I have come
across one problem with SQLite.
In journal_mode=delete the selection is database locked.
When one thread does a TRANSACTION on the
On 3 Nov 2013, at 1:24pm, Raheel Gupta raheel...@gmail.com wrote:
In order to avoid this, I had to use journal_mode=wal so that two threads
dont have to wait when they both are doing SELECTs which might be taking
3-5 seconds to process.
I assume you have designed your indexes specifically
SQLite do not use row level locking, but db level locking, so it was
the right behavior the second thread was blocked.
For innodb like in SQLite, Oracle have SQLite compatible API, but use
BDB backend.
Since BDB use MVCC (row/page level locking), your threads only blocked
if they will write in
Aris Setyawan wrote:
SQLite do not use row level locking, but db level locking, so it was
the right behavior the second thread was blocked.
For innodb like in SQLite, Oracle have SQLite compatible API, but use
BDB backend.
Since BDB use MVCC (row/page level locking), your threads only blocked
SQLightning replaces the SQLite backend with Symas' LMDB, which also uses
MVCC
and thus supports high concurrency. It is also many times faster than
BerkeleyDB and vanilla SQLite.
Your MVCC is different compared to InnoDB or BDB locking. Every one
should carefully read each DB's doc, then
Aris Setyawan wrote:
SQLightning replaces the SQLite backend with Symas' LMDB, which also uses
MVCC
and thus supports high concurrency. It is also many times faster than
BerkeleyDB and vanilla SQLite.
Your MVCC is different compared to InnoDB or BDB locking. Every one
should carefully read
@Howard I had tested your code earlier but it didnt seem to be stable and
getting it to run was a task. Also I learnt that it is a in-memory
database.
@Aris are you saying BDB is better and faster than SQLite ?
On Sun, Nov 3, 2013 at 8:28 PM, Howard Chu h...@symas.com wrote:
Aris Setyawan
On 2012/04/08 Yuriy Kaminskiy wrote:
On 2011/10/23, Yuriy Kaminskiy wrote:
Yuriy Kaminskiy wrote:
Yuriy Kaminskiy wrote:
Yuriy Kaminskiy wrote:
When WHERE condition is constant, there are no need to evaluate and check
it for
each row. It works, but only partially:
...
[In fact, you can
On Sat, 2 Nov 2013 18:06:30 +0100
Gert Van Assche ger...@datamundi.be wrote:
CREATE TABLE T (N, V, G);
INSERT INTO T VALUES('a', 1, 'x');
INSERT INTO T VALUES('b', 3, 'x');
INSERT INTO T VALUES('c', null, 'x');
INSERT INTO T VALUES('d', 80, 'y');
INSERT INTO T VALUES('e', null, 'y');
Raheel Gupta wrote:
@Howard I had tested your code earlier but it didnt seem to be stable and
getting it to run was a task. Also I learnt that it is a in-memory
database.
False. LMDB is a memory-mapped disk database, that is not the same as an
in-memory database.
@Aris are you saying BDB is
Aris Setyawan wrote:
SQLightning replaces the SQLite backend with Symas' LMDB, which also uses
MVCC
and thus supports high concurrency. It is also many times faster than
BerkeleyDB and vanilla SQLite.
Your MVCC is different compared to InnoDB or BDB locking. Every one
should carefully read
I just looked, sophia is nothing special. See these microbench results.
http://pastebin.com/cFK1JsCN
LMDB's codebase is still smaller and faster. Nothing else touches LMDB's
read
speed.
Focus to the write number.
You are using SSD or HDD?
On 11/4/13, Howard Chu h...@symas.com wrote:
Aris
A small issue has arisen that the local powers may want to be aware of. In
Visual Studio 2013, which uses the Windows 8.1 Platform SDK, they've marked
GetVersionEx as deprecated, trying to supercede it through to VerifyVersionInfo
and some other hardcoded macros based on that call that the new
I've worked around this issue a separate way, but I'd like to understand what
went wrong in the first place here. I have an FTS3 table, and if I query with
the following:
SELECT * FROM table WHERE keywords MATCH '(blah!)'
I get the following error:
malformed MATCH expression:_[(blah!)]
If I
Hello,
select date('2013-11-04') - Works well
select date('2013-11-4') - Not working
Is there a way to make the second form working? Currently, I handle this
at the application side. If month/day is less than 10, then prefix it
with 0. But I'm wondering is there a better way to do this at
On Mon, Nov 4, 2013 at 1:38 AM, David de Regt dav...@mylollc.com wrote:
I've worked around this issue a separate way, but I'd like to understand
what went wrong in the first place here. I have an FTS3 table, and if I
query with the following:
SELECT * FROM table WHERE keywords MATCH
I realize that the query is being parsed with the enhanced query syntax since I
added parenthesis (and have that compile flag enabled), but why does the
exclamation point at the end cause an error? It seems like it should be just
ignored, given the default tokenizer.
-Original
Navaneeth K N wrote:
select date('2013-11-04') - Works well
select date('2013-11-4') - Not working
Is there a way to make the second form working?
Only by inserting a zero into the string (which isn't easy
with the built-in SQL functions).
Regards,
Clemens
21 matches
Mail list logo
