When I compare the database bytes before and after the 2nd
process VACUUM these bytes differ:
zero-basedvalue value
byte offset beforeafter my guess of what it is
2nd VAC 2nd VAC
--- --- --- --
272 5
Regarding http://www.sqlite.org/cvstrac/tktview?tn=2804 ...
I'm confused by the explanation.
Ignoring the PRAGMA for the moment, I was surprised that DESC
indexes were not available after a reconnect and VACUUM, as shown
in the example:
$ rm -f foo.db
$ ./sqlite3-3.5.3.bin foo.db
SQLite version
You will always get much faster searching using a flat file and a
grep-like search. For the search you quote you can do better than egrep
with an integrated search algorithm like Boyer-Moore.
This is no reflection on Sqlite, it is not intended to be a replacement
for grep.
Spiros Ioannou
On 11/27/07, Spiros Ioannou <[EMAIL PROTECTED]> wrote:
> I had a 135MB, 1256132 lines, '@' separated text file containing
> various words and text fields (like a dictionary).
> Example record:
> [EMAIL PROTECTED]@[EMAIL PROTECTED],[EMAIL PROTECTED] altana : μικρός
> ανθόκηπος - εξώστης,
>
On 11/25/07, Ralf Junker <[EMAIL PROTECTED]> wrote:
> Imagine that a SQLite3 database opened in a custom application with a
> registered a collation sequence named "unknown" has created the following
> table:
>
> CREATE TABLE a (b COLLATE unknown);
>
> Now open this table in the default
Ralf Junker wrote:
Are there any opinions on this list, or should I just post a bug ticket?
Ralf
Imagine that a SQLite3 database opened in a custom application with a registered a
collation sequence named "unknown" has created the following table:
CREATE TABLE a (b COLLATE unknown);
See also sqlite3_sql() if sqlite3_prepare_v2() or
sqlite3_prepare16_v2() was used.
http://www.sqlite.org/cvstrac/chngview?cn=4543
--- Igor Tandetnik <[EMAIL PROTECTED]> wrote:
> Evans, Mark (Tandem) <[EMAIL PROTECTED]> wrote:
> > Would I be the first person to wish there were a way for, say, a
Evans, Mark (Tandem) <[EMAIL PROTECTED]> wrote:
Would I be the first person to wish there were a way for, say, a JDBC
driver that uses SQLite to be able to tell what kind of SQL statement
it is executing?
sqlite3_column_count returns 0 for a non-SELECT statement, and a
non-zero value for
Greetings lite-meisters,
Would I be the first person to wish there were a way for, say, a JDBC driver
that uses SQLite to be able to tell what kind of SQL statement it is executing?
Unless I missed an API, sqlite3_step() indicates either a SELECT that matched
at least one row, or any
[EMAIL PROTECTED] wrote:
Gerry Snyder <[EMAIL PROTECTED]> wrote:
The tclsqlite.dll file will follow soon?
Try it now, please.
Downloaded and in use.
Thanks much.
I hope that things work out and you are able to keep including FTS3 in
the binaries. I think it will be a plus for
Gerry Snyder <[EMAIL PROTECTED]> wrote:
> The tclsqlite.dll file will follow soon?
>
Try it now, please.
--
D. Richard Hipp <[EMAIL PROTECTED]>
-
To unsubscribe, send email to [EMAIL PROTECTED]
On Tue, 27 Nov 2007 14:54:32 +, [EMAIL PROTECTED] wrote:
>Jarl Friis <[EMAIL PROTECTED]> wrote:
>> [EMAIL PROTECTED] writes:
>>
>> >
>> > The file format is portable.
>> >
>> > However, if you store UTF16le data, there is a performance
>> > penalty for extracting it on a UTF16be machine.
>>
Thanks for the quick answer. This product is great! Bye!
Clodo <[EMAIL PROTECTED]> wrote:
But a changelogs say:
"Version 3.3.0 adds support for CHECK constraints, DESC indices, "
I use the 3.5.2 version.
What's the status/problem about that?
How i can re-write the first select above to
Hello,
I had a 135MB, 1256132 lines, '@' separated text file containing
various words and text fields (like a dictionary).
Example record:
[EMAIL PROTECTED]@[EMAIL PROTECTED],[EMAIL PROTECTED] altana : μικρός ανθόκηπος - εξώστης,
ταράτσα@@@
I imported the data in sqlite3.3.6 but
--- [EMAIL PROTECTED] wrote:
> DESC indices requires a backwards-compatible file format
> changes. Older versions of SQLite (prior to 3.3.0) cannot
> read or write databases that make use of DESC indicdes.
> To preserve compatibility, SQLite generates databases in
> the old format by default.
Gerry Snyder <[EMAIL PROTECTED]> wrote:
> The tclsqlite.dll file will follow soon?
>
> Gerry
>
Some kind of build problem happened. I'll have to
debug it. But I have several other more pressing
issue ahead of this on the queue.
You want to try to patch up the mkdll.sh script for
me, Gerry
Please note: typo on page http://sqlite.org/releaselog/3_5_3.html
"TCL interfaced"
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 27, 2007 9:56 AM
To: sqlite-users@sqlite.org
Subject: [sqlite] Version 3.5.3
Importance: High
SQLite version
Clodo <[EMAIL PROTECTED]> wrote:
>
> But a changelogs say:
> "Version 3.3.0 adds support for CHECK constraints, DESC indices, "
>
> I use the 3.5.2 version.
> What's the status/problem about that?
> How i can re-write the first select above to use an index on both fields?
> Thanks!
>
DESC
The tclsqlite.dll file will follow soon?
Gerry
-
To unsubscribe, send email to [EMAIL PROTECTED]
-
Hi to all, i have a problem with indexes. For example:
CREATE TABLE T1 (
a text,
b text
);
CREATE INDEX I1 on T1 (a asc, b desc);
1' query:
explain query plan select * from t1 order by a asc, b desc limit 10
output detail-> TABLE T1
2' query:
explain query plan select * from t1 order by a
Filipe Fernandes <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > SQLite version 3.5.3 is now up on the website:
> >
> >http://www.sqlite.org/
> >
>
> Sorry if I missed something here... it's not clear to me how I can
> download the documentation. It's not included in the
[EMAIL PROTECTED] wrote:
> SQLite version 3.5.3 is now up on the website:
>
>http://www.sqlite.org/
>
Sorry if I missed something here... it's not clear to me how I can
download the documentation. It's not included in the sqlite-3.5.3.tar.gz
file as specified in the download area. The
--- [EMAIL PROTECTED] wrote:
> SQLite version 3.5.3 is now up on the website:
> As always, please report any problems.
http://www.sqlite.org/releaselog/3_5_3.html
* DISTINCT can now make use of an INDEX in some cases.
=?ISO-8859-1?Q?Lu=EDs_Santos?= <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have an SQLite with SEE.
>
> I am currently having some troubles concerning memory allocation (I'm
> getting a MALLOC_ERROR in strange circumstances), and I am trying to
> upgrade my SQLite from 3.5.1 to 3.5.2 to see if
Hi,
I have an SQLite with SEE.
I am currently having some troubles concerning memory allocation (I'm
getting a MALLOC_ERROR in strange circumstances), and I am trying to
upgrade my SQLite from 3.5.1 to 3.5.2 to see if there's any change to my
problem.
Should I have some other concern about
"Michael Ruck" <[EMAIL PROTECTED]> wrote:
> Are all CREATE ... statements transactional or is only CREATE TABLE
> transactional?
>
All.
--
D. Richard Hipp <[EMAIL PROTECTED]>
-
To unsubscribe, send email to [EMAIL
On Nov 27, 2007, at 10:27 PM, Michael Ruck wrote:
Are all CREATE ... statements transactional or is only CREATE TABLE
transactional?
All of the CREATE and DROP statements work properly within
transactions. If the containing transaction is rolled back, the CREATE
or DROP is rolled back along
"Igor Sereda" <[EMAIL PROTECTED]> wrote:
> I noticed that CREATE TABLE works well within a transaction, which was a
> pleasant surprise. I can create a table and insert some rows in it, all
> quite ACIDly - wow!
>
> My question is, is that a declared contract or just a peculiarity that
> may
Are all CREATE ... statements transactional or is only CREATE TABLE
transactional?
Mike
> -Ursprüngliche Nachricht-
> Von: Dan [mailto:[EMAIL PROTECTED]
> Gesendet: Dienstag, 27. November 2007 15:59
> An: sqlite-users@sqlite.org
> Betreff: Re: [sqlite] Transactional DDL
>
>
> On Nov
On Nov 27, 2007, at 9:47 PM, Igor Sereda wrote:
I noticed that CREATE TABLE works well within a transaction, which
was a pleasant surprise. I can create a table and insert some rows
in it, all quite ACIDly - wow!
My question is, is that a declared contract or just a peculiarity
that may
Jarl Friis <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] writes:
>
> >
> > The file format is portable.
> >
> > However, if you store UTF16le data, there is a performance
> > penalty for extracting it on a UTF16be machine.
>
> Thanks. That made the answer very clear. Could that clear
I noticed that CREATE TABLE works well within a transaction, which was a
pleasant surprise. I can create a table and insert some rows in it, all quite
ACIDly - wow!
My question is, is that a declared contract or just a peculiarity that may
disappear in future versions? I couldn't find any
[EMAIL PROTECTED] writes:
>
> The file format is portable.
>
> However, if you store UTF16le data, there is a performance
> penalty for extracting it on a UTF16be machine.
Thanks. That made the answer very clear. Could that clear information
be put somewhere in the documetation pages or wiki.
Jarl Friis <[EMAIL PROTECTED]> wrote:
> "Nuno Lucas" <[EMAIL PROTECTED]> writes:
>
> > If you will be sharing databases between different endienness
> > systems then you care, so you will take appropriate actions to have
> > the best result. The same is true with any other portable file
> >
On Nov 27, 2007, at 7:26 PM, Jarl Friis wrote:
"Nuno Lucas" <[EMAIL PROTECTED]> writes:
If you will be sharing databases between different endienness
systems then you care, so you will take appropriate actions to have
the best result. The same is true with any other portable file
format.
"Nuno Lucas" <[EMAIL PROTECTED]> writes:
> If you will be sharing databases between different endienness
> systems then you care, so you will take appropriate actions to have
> the best result. The same is true with any other portable file
> format.
So my question boils down to: Is the SQLite
On Tue, 2007-11-27 at 11:45 +0300, Igor Sereda wrote:
> It does look good, but it's not quite usable with large databases though.
> For example, I couldn't wait till Browse and Search page showed a 2 million
> rows table -- it seemed to load everything into memory, eating up resources
> and
It does look good, but it's not quite usable with large databases though.
For example, I couldn't wait till Browse and Search page showed a 2 million
rows table -- it seemed to load everything into memory, eating up resources
and causing Firefox to come up with "stop script" dialogs.
Otherwise,
38 matches
Mail list logo
