On Wed, Aug 5, 2009 at 5:37 PM, Lukas Haase wrote:
> Hi list,
>
> I have a huge problem: A database with 2 HTML fragements should
> contain a fulltext index. For that reason I put all data into a virtual
> table:
>
> CREATE VIRTUAL TABLE topics USING fts3(
> topicID INTEGER,
> top
This is a deep problem. You need a segmenter (*) to tell you how you
can break the words into sub-words, then you need to build a tokenizer
which will return the right pieces. This should be possible with
what's in there, but you're definitely going to have to sit down with
the source code and wa
fts has an implicit index on the docid (aka rowid), and a fulltext
index on the terms in the columns. All columns are treated as TEXT,
you can say INTEGER or VARCHAR, but they are TEXT.
The end of this page:
http://code.google.com/apis/gears/api_database.html
has an example of how you might co
D. Richard Hipp wrote:
> On Aug 10, 2009, at 5:11 PM, Andreas Kupries wrote:
>>> The amalgamation has been rebuilt and a new (corrected) version is on
>>> the website.
>>>
>>> The underlying problem is that a new SQLITE_API is added to the
>>> sqlite3.h file every time you do "make sqlite3.c". So
On Aug 10, 2009, at 5:11 PM, Andreas Kupries wrote:
>>
>> The amalgamation has been rebuilt and a new (corrected) version is on
>> the website.
>>
>> The underlying problem is that a new SQLITE_API is added to the
>> sqlite3.h file every time you do "make sqlite3.c". So if you do that
>> multiple
D. Richard Hipp wrote:
> On Aug 10, 2009, at 3:30 PM, Roger Binns wrote:
>> There is a problem in the amalgamation (.tar.gz but not .zip) where
>> SQLITE_API is repeated multiple times making the code invalid if
>> defined to
>> anything. Example:
>>
>>> SQLITE_API const char sqlite3_version[] =
On Aug 10, 2009, at 3:30 PM, Roger Binns wrote:
>
> There is a problem in the amalgamation (.tar.gz but not .zip) where
> SQLITE_API is repeated multiple times making the code invalid if
> defined to
> anything. Example:
>
>> SQLITE_API const char sqlite3_version[] = SQLITE_VERSION;
>> SQLITE_AP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D. Richard Hipp wrote:
> SQLite version 3.6.17 is now available
There is a problem in the amalgamation (.tar.gz but not .zip) where
SQLITE_API is repeated multiple times making the code invalid if defined to
anything. Example:
> SQLITE_API const char
On Mon, Aug 10, 2009 at 2:25 PM, Leo Freitag wrote:
> Hello,
>
> in table haupt I store information about group, singer, song, voice and
> datestamp.
>
> [CODE]
> CREATE TABLE 'haupt' ('id' INTEGER PRIMARY KEY, 'group' INTEGER,
> 'singer' INTEGER, 'song' INTEGER,
> 'voice' INTEGER, 'datestamp' TEX
Regarding: "1. Provide a pre-compiled 2,1 (for Windows), or ..."
Hi Rod,
IN A SEPARATE PRIVATE EMAIL TO YOU I've attached a windows executable
command line utility for version 2.13.
Conversion is easy. Open the database using the version 2 executable
and use commands like ".output ascii.sql
Hello,
in table haupt I store information about group, singer, song, voice and
datestamp.
[CODE]
CREATE TABLE 'haupt' ('id' INTEGER PRIMARY KEY, 'group' INTEGER,
'singer' INTEGER, 'song' INTEGER,
'voice' INTEGER, 'datestamp' TEXT);
INSERT INTO "haupt" VALUES(1, 1, 1, 1, 11, '2009-08-01');
INSE
We had a thread not long ago about pre-built packages for SQLite. I just
downloaded the 3.6.17 source, built it, and upgraded from 3.6.16. Works
fine. So, if anyone wants a package for Slackware-12.2, ask and ye shall
receive.
Rich
--
Richard B. Shepard, Ph.D. | Integrity
On Mon, 10 Aug 2009, Rod Dav4is wrote:
> Perhaps the version 3.6 db manager will automatically convert my 2.1 to
> the new 3.6 format (or is that too much to hope for?).
Knowing nothing about any version of Windows, I suggest that you make a
copy of the exiting file and try opening it in the l
I'm breaking in a new PC, with Vista fighting me every inch of the way!
*My immediate problem*: I have a rather large v2.1 SQLite db (~26MB) and
I seem to have lost my copy of SQLite 2.1. Can someone help me out:
1. Provide a pre-compiled 2,1 (for Windows), or
2. Provide an easy conversion
On Mon, 10 Aug 2009, D. Richard Hipp wrote:
> SQLite version 3.6.17 is now available on the SQLite website:
[...]
> This is the first release of SQLite after 100% branch test coverage of
> the SQLite core was achieved. The effort to bring SQLite up to 100%
Sounds good to me! :-)
Mak
SQLite version 3.6.17 is now available on the SQLite website:
http://www.sqlite.org/
http://www.sqlite.org/download.html
This is the first release of SQLite after 100% branch test coverage of
the SQLite core was achieved. The effort to bring SQLite up to 100%
branch test coverage s
Hi Nikolaus,
Interesting to read your findings. I assume you finally disallowed
read_uncommitted. Trying to explain why the wait times can get longer, I come
to two reasons.
- the time slots where a read-lock is obtained become smaller.
This can be significant if there are a lot of transaction
17 matches
Mail list logo
