Aris Setyawan wrote:
Hi Howard,
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.
This is micro benchmark from sophia author compare with lmdb.
http://sphia
Hi Howard,
> 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.
This is micro benchmark from sophia author compare with lmdb.
http://sphia.org/benchmark
On 04.11.2013 11:46, Rafa de Miguel wrote:
Yes, I knew that but that info it doesn't really help me too much
FWIW: You probably are aware of this too, but just in case: On the
browsers, especially these without build-in WebSQL (sqlite) support, the
developer can fallback to a C to LLVM IR to
I just ran into a possible bug when trying to add some debugging ability to my
app. I have a global #define for the max # of bindable columns (to tweak for
perf/statement cache/etc.), and I wanted to make it so I could set it to 0 to
basically disable my statement preparation code, so that I co
>> SQLite4 still in development phase. It is not production ready.
But isnt that the same thing as BDB or Kyoto i.e. a Key Value store ?
>> If you have many core of processors [and big RAM], then I recommend
BDB Sql over Sqlite.
I have large space and around 4GB of ram with Dual Cores to Quad Co
> Will SQLite4 be a better solution for me then ?
SQLite4 still in development phase. It is not production ready.
> Also @aris do you recommend BDB over Sqlite for 1-10 Billion records ?
If you have many core of processors [and big RAM], then I recommend
BDB Sql over Sqlite. Because you can have
2013/11/4 Simon Slavin :
> On 4 Nov 2013, at 6:32am, David de Regt wrote:
>> 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 tha
On 4 Nov 2013, at 7:36am, Clemens Ladisch wrote:
> 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
On 4 Nov 2013, at 6:32am, David de Regt wrote:
> 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 SDK implements.
Thanks James -- the select query is something I could do, but the update
one I could not get that one right.
I was considering to create a new table based on the select query, but
since the real data set is millions of records, an update was the best
solution.
As always, thanks for your help.
g
Will SQLite4 be a better solution for me then ?
Also @aris do you recommend BDB over Sqlite for 1-10 Billion records ?
On Mon, Nov 4, 2013 at 8:03 AM, Aris Setyawan wrote:
> > I just looked, sophia is nothing special. See these microbench results.
> > http://pastebin.com/cFK1JsCN
> >
> > LMDB'
Thanks Clemens
Flash gives the error - no such function: 'sqlite_version'
SQLite Administrator says 3.5.1
I'll see what the Adobe community say.
On Mon, Nov 4, 2013 at 9:30 PM, Clemens Ladisch wrote:
> SongbookDB wrote:
> > The database has an index that is being used according to EXPLAIN
SongbookDB wrote:
> The database has an index that is being used according to EXPLAIN QUERY
> PLAN in SQLite Administrator. Does Flash use the same SQL code?
Probably not. Try "SELECT sqlite_version();".
Regards,
Clemens
___
sqlite-users mailing list
If you are using System.Data.SQLite with the provided Encryption you may run
into the same problem as I had.
http://www.mail-archive.com/sqlite-users%40sqlite.org/msg66194.html
As Richard already clarified, this encryption is not officially supported by
the SQLite team and is only there for bac
Dear SQLite users,
I'd like to present you Unicode support extension i've implemented for
SQLite, it does full Unicode (6.3.0) collations, case mapping and
untailored ordering, and takes only ~100Kb to do that if you link it
statically. It's also open source and free (MIT license):
https://bi
Ah - thanks Clemens - that worked REALLY well!
On Sun, Nov 3, 2013 at 10:22 PM, Clemens Ladisch wrote:
> 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 * FR
Hi
Just wondering if anyone has heard of Flash adding time to queries?
I have a query that is taking almost 5 seconds on a database in Flash, yet
when I put the same query into SQLite Administrator with that database
loaded, it takes 15ms.
I set up a flash timer, and start it just before...
sq
Yes, I knew that but that info it doesn't really help me too much
El 04/11/13 10:33, Stephan Beal escribió:
On Mon, Nov 4, 2013 at 10:26 AM, Rafa de Miguel <
rafael.demig...@openbravo.com> wrote:
Do I have control about the WebSQL version or it's Chrome whom decide it?
FWIW: i don't know if
Thanks Simon
I'm yet to get to setting up a new table with COLLATE NOCASE columns and
copy the old table's data into it.
On Sun, Nov 3, 2013 at 11:01 PM, Simon Slavin wrote:
>
> On 3 Nov 2013, at 3:24am, SongbookDB wrote:
>
> > WHERE Language !="" COLLATE NOCASE
> > ORDER BY Language COLLATE
On Mon, Nov 4, 2013 at 10:26 AM, Rafa de Miguel <
rafael.demig...@openbravo.com> wrote:
> Do I have control about the WebSQL version or it's Chrome whom decide it?
>
FWIW: i don't know if this matters to you, but WebSQL was dropped from
HTML5-related standardization efforts some time ago (2+ year
Thanks Clemens,
I'm not sure how to do that.
I'm using Google Chrome Version: 28.0.1500.52 which I think is the latest
stable version.
Do I have control about the WebSQL version or it's Chrome whom decide it?
Thanks in advance,
Rafa
El 04/11/13 09:30, Clemens Ladisch escribió:
Rafa de
On 11/04/2013 01:58 PM, David de Regt wrote:
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
Rafa de Miguel wrote:
> Is there a way to know which constraint is being violated when you receive
> the message constraint error 19:
>
> In example: my_column_name UNIQUE constraint
Upgrade SQLite:
sqlite> create table t(x unique);
sqlite> insert into t values(1);
sqlite> insert into t values(1
Hello all,
Is there a way to know which constraint is being violated when you receive
the message constraint error 19:
http://www.sqlite.org/c3ref/c_abort.html #define SQLITE_CONSTRAINT 19 /*
Abort due to constraint violation */
In example: my_column_name UNIQUE constraint
I'm using Web
24 matches
Mail list logo
