On 21 Nov 2011, at 3:13am, Mohit Sindhwani wrote:
> I think my examples muddied the waters. I have looked at Section 3 of the
> FTS documents and that lets me bring back the "full result" that matches -
> so, if I search for 'ling j', it can tell me that the result that matches is
> 'james li
Hi Abhinav,
On 21/11/2011 2:52 AM, Abhinav Upadhyay wrote:
On Mon, Nov 21, 2011 at 12:17 AM, Mohit Sindhwani wrote:
What I'd like to be able to do is something like this:
- let's say that the FTS4 table has values such as:
* mohit sindhwani, onghu
* john doe, gmail
* james ling, alibaba
* john
I am not not working that close to the SQLite source to talk about
sqlite3_step etc.
as I am using a VB wrapper. Still, I suppose what you say still applies.
As it turns out and can now beforehand (without checking for
non-consecutive id numbers)
how many records should be fetched, so with that thi
On Mon, Nov 21, 2011 at 12:17 AM, Mohit Sindhwani wrote:
> Hi, I'm finding my way through FTS3/FTS4 to replace some of the old code
> that we have for searching terms within titles. I now know that FTS3/4
> should be the way to proceed.
>
> So far, I have this:
> - an FTS4 table that has two colu
Hi, I'm finding my way through FTS3/FTS4 to replace some of the old code
that we have for searching terms within titles. I now know that FTS3/4
should be the way to proceed.
So far, I have this:
- an FTS4 table that has two columns: title (main column), ext (certain
conditions to match)
- an
Matt Young wrote:
> In the documentation on trigger, begin has no semicolon, and it works.
> From the command line, I can begin and end transaction, but I need the
> semicolon after begin. Is there a difference?
BEGIN keyword is used in two different contexts, and has different meanings in
these
Bart Smissaert wrote:
> In fact when doing something as you suggest:
> select * from MyTable where ID <= 14 order by ID desc
> I can make it a lot more efficient by adding a limit as not many
> records will be needed.
There's no difference between adding a LIMIT N clause to the query, and simply
Bernd wrote:
> I found that table aliases are repeated in the headers of compound
> queries. Is this intentional and/or documented somewhere?
http://www.sqlite.org/c3ref/column_name.html
The name of a result column is the value of the "AS" clause for that column, if
there is an AS clause. If the
Matt Young wrote:
> Well, it was listed as an initial option o the trigger
What do you mean, listed? Listed where and by whom?
--
Igor Tandetnik
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqli
Simon Slavin wrote:
> SELECT in a TRIGGER doesn't report its results to anything. The only reason
> I can think of for doing one is it uses a function
> that has some weird side-effect.
Like, say, RAISE.
--
Igor Tandetnik
___
sqlite-users mailing
On Sun, Nov 20, 2011 at 1:21 PM, Richard Hipp wrote:
> On Sun, Nov 20, 2011 at 6:53 AM, Tal Tabakman wrote:
>
>> in a continuation to the below, it seems I get the following extended err
>> code
>> SQLITE_IOERR_WRITE
>> what are the reasons for that one ? is it a symptom of mem blow-up ?
>> cheers
On Sun, Nov 20, 2011 at 6:53 AM, Tal Tabakman wrote:
> in a continuation to the below, it seems I get the following extended err
> code
> SQLITE_IOERR_WRITE
> what are the reasons for that one ? is it a symptom of mem blow-up ?
> cheers
> Tal
>
>
What operating system did you say you were using?
in a continuation to the below, it seems I get the following extended err
code
SQLITE_IOERR_WRITE
what are the reasons for that one ? is it a symptom of mem blow-up ?
cheers
Tal
>* Hi Guys,*>* in which cases can I get sqlite3 error "disk I/O error", is it
>only when*>* disk is full ?*>* any other
in a continuation to the below, it seems I get the following extended err
code
SQLITE_IOERR_WRITE
what are the reasons for that one ? is it a symptom of mem blow-up ?
cheers
Tal
>* Hi Guys,*>* in which cases can I get sqlite3 error "disk I/O error", is it
>only when*>* disk is full ?*>* any other
Thanks; that to me looks a truly amazing SQL!
As you say doing this in code might be more efficient and definitely
less confusing.
In fact when doing something as you suggest:
select * from MyTable where ID <= 14 order by ID desc
I can make it a lot more efficient by adding a limit as not many
reco
Hi list,
I found that table aliases are repeated in the headers of compound
queries. Is this intentional and/or documented somewhere?
I'm asking, because it forces one to either already alias the columns in
the query or use the aliased column name in the DataReader (I'm using
the .NET provider)
Cool beans, perhaps this should be added to the docs!
On Sun, Nov 20, 2011 at 1:36 AM, Dan Kennedy wrote:
> On 11/20/2011 04:00 PM, Yang Zhang wrote:
>>
>> Out of curiosity, what's the proper way to change the temp directory
>> (say, to avoid "Error: database or disk full" errors on vacuum, which
On 11/20/2011 04:00 PM, Yang Zhang wrote:
Out of curiosity, what's the proper way to change the temp directory
(say, to avoid "Error: database or disk full" errors on vacuum, which
I ran into)? temp_store_directory has been working for me but it's
deprecated and may be elided from builds. Is th
Out of curiosity, what's the proper way to change the temp directory
(say, to avoid "Error: database or disk full" errors on vacuum, which
I ran into)? temp_store_directory has been working for me but it's
deprecated and may be elided from builds. Is the only option to
recompile sqlite? Thanks.
In the documentation on trigger, begin has no semicolon, and it works.
From the command line, I can begin and end transaction, but I need the
semicolon after begin. Is there a difference?
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlit
20 matches
Mail list logo