On 1 Oct 2011, at 12:37am, Petite Abeille wrote:
> On Sep 21, 2011, at 2:19 AM, Richard Hipp wrote:
>
>> If you are storing large BLOBs in SQLite, can you read them faster if they
>> are stored directly in the database file, or can you get to them quicker if
>> you store just a filename in the
On Sep 21, 2011, at 2:19 AM, Richard Hipp wrote:
> If you are storing large BLOBs in SQLite, can you read them faster if they
> are stored directly in the database file, or can you get to them quicker if
> you store just a filename in the database and read the BLOB content from a
> separate
As an addition to this post.
Once I was able to make JDBC connections to SQLite on my system I found any
volume of connections lead to intermittent errors in the pure java sqlite jdbc
providers I was using.
Things like:
org.ibex.nestedvm.Runtime$FaultException:
On Sep 30, 2011, at 2:34 PM, Igor Tandetnik wrote:
>> Any gotchas in using blob as keys (unique or otherwise)?
>
> None that I know of.
Thanks Igor :)
___
sqlite-users mailing list
sqlite-users@sqlite.org
Filip Navara writes:
>
> On Fri, Sep 30, 2011 at 2:21 PM, Reg Server wrote:
> [snip]
> > I don't have Mac but I tried mentioned steps using sqlite3.exe using both
> > versions 3.7.8 and 3.7.5. It crashed every time.
> >
> > I'm don't know where to get older
On Fri, Sep 30, 2011 at 2:21 PM, Reg Server wrote:
[snip]
> I don't have Mac but I tried mentioned steps using sqlite3.exe using both
> versions 3.7.8 and 3.7.5. It crashed every time.
>
> I'm don't know where to get older versions to investigate where the crash
> started
Petite Abeille wrote:
> From an efficiency point of view, would one be better off storing that key as
> a blob or text? In other words, store the raw byte
> sequence directly or use a hex text representation of it?
Blob
> So, binary:
>
>hashblob not
Simon Slavin writes:
>
>
> On 30 Sep 2011, at 11:09am, Filip Navara wrote:
>
> > Reproduced with the following steps:
> >
> >> sqlite3 test.db
> > pragma count_changes=1;
> > create table a (a);
> > vacuum;
> >
> > (SQLite 3.7.8 on Windows)
>
> On my Mac
>
> SQLite version
On 30 Sep 2011, at 11:09am, Filip Navara wrote:
> Reproduced with the following steps:
>
>> sqlite3 test.db
> pragma count_changes=1;
> create table a (a);
> vacuum;
>
> (SQLite 3.7.8 on Windows)
On my Mac
SQLite version 3.7.5
Enter ".help" for instructions
Enter SQL statements terminated
Reproduced with the following steps:
> sqlite3 test.db
pragma count_changes=1;
create table a (a);
vacuum;
(SQLite 3.7.8 on Windows)
Best regards,
Filip Navara
___
sqlite-users mailing list
sqlite-users@sqlite.org
Hi all,
I am trying to update our application to use latest SQLite library. In many
places of the code we were using data returned from INSERT, UPDATE, DELETE
commands when count_changes pragma is set to 1. First thing I noticed is that
this pragma is now deprecated. But, it still works
Hello.
I've always got great help in this list so I thank in advance who posts
here and who will answer to my question.
I've started to use FTS in a web site for search thru a table of sites.
Given a main table containing, among others, fields "id", "url", "nome"
(title) and "descrizione"
Hello,
Say one has a hash value as an indexed key for a table.
>From an efficiency point of view, would one be better off storing that key as
>a blob or text? In other words, store the raw byte sequence directly or use a
>hex text representation of it?
So, binary:
hashblob
13 matches
Mail list logo