look at the glob command it works like like except uses the unix file name
globbing style of matching
not quite a grep
select * from table where a glob '[abc]foobar*';
At 06:47 PM 7/5/2005, you wrote:
like this?
select * from table where a like '%abc%';
SQLite also makes it easy to write
like this?
select * from table where a like '%abc%';
SQLite also makes it easy to write your own functions. That way you
can define other matching algorithms (eg Jaro-Winkler).
Roger
> From: Stephen Leaf <[EMAIL PROTECTED]>
> Organization: SMiLeaf
> To: sqlite-users@sqlite.org
> Date: Tue, 5 Jul 2005 18:06:39 -0500
> Subject: Re: [sqlite] Does SQLite have a fulltext search like MySQL?
>
> On Tuesday 05 July 2005 04:48 pm, Michael Grice wrote:
> > If not, are there plans to add
On Tuesday 05 July 2005 04:48 pm, Michael Grice wrote:
> If not, are there plans to add this?
>
> I'm just a NOOB, looking to see what all SQLite can do for me, before
> I go too far down this road.
>
> Thx.
like this?
select * from table where a like '%abc%';
On Tuesday 05 July 2005 05:31 pm, Tom Shaw wrote:
> Is there an easy way to perform a search on VARCHAR/CHAR/TEXT column
> for those entries that has strings that are longer than x without
> writing my own comparitor? I am using SQLite in a PHP environment, I
> am looking for an intrinsic function
Is there an easy way to perform a search on VARCHAR/CHAR/TEXT column
for those entries that has strings that are longer than x without
writing my own comparitor? I am using SQLite in a PHP environment, I
am looking for an intrinsic function that would run natively rather
than a interpretive
If not, are there plans to add this?
I'm just a NOOB, looking to see what all SQLite can do for me, before
I go too far down this road.
Thx.
On Tuesday 05 July 2005 01:23 pm, jack wu wrote:
> one more question if i may. what should i do if i 'd
> like to have two columns, one for Date, one for Time
> of the day. most of the times, i 'd like to query by
> Date only but i want to display date and time at the
> same time. is
one more question if i may. what should i do if i 'd
like to have two columns, one for Date, one for Time
of the day. most of the times, i 'd like to query by
Date only but i want to display date and time at the
same time. is julianday('2005-07-01') going to store
any time information? Thanks.
jack wu wrote:
i am trying to run some web search like query. the one
that returns a total number of results and only
presents the first 20, then allows user to click on
next to go to the next 20 etc.
has anyone done this before? i suppose i would use
LIMIT or OFFSET in the select statement,
On Tuesday 05 July 2005 09:53 am, Cory Nelson wrote:
> Just an educated guess, but probably because sqlite tries to be as
> minimal as possible. Which I have no complaints with, as comparing a
> double will likely be faster than comparing a string.
I personally store all mine like this anyway
Just an educated guess, but probably because sqlite tries to be as
minimal as possible. Which I have no complaints with, as comparing a
double will likely be faster than comparing a string.
On 7/5/05, Johan Danielsson <[EMAIL PROTECTED]> wrote:
> Cory Nelson <[EMAIL PROTECTED]> writes:
>
> >
AS a DB rookie, I have replaced the .txt files in an Tcl/Tk application with
a SQLite database, so it still reads very much like file I/O. While in a
loop I wrote several records to my files, so now I simply do an INSERT.
I keep reading that you optimize performance by using transactions, so
Cory Nelson <[EMAIL PROTECTED]> writes:
> create table t_foo(bar real);
> insert into t_foo values(julianday('2005-07-01'));
Is there any advantage to this compared to storing dates as strings in
(for instance) ISO8601 format?
/Johan
create table t_foo(bar real);
insert into t_foo values(julianday('2005-07-01'));
On 7/4/05, jack wu <[EMAIL PROTECTED]> wrote:
> Cory, thanks for the information. the wiki talks about
> time functions. what should we do when defining the
> table columns? should i just use REAL? can you give a
>
Hi!
If I do this*, is anyone else interested in it? Obviously it would
be a compile time option, as it would probably impact performance
(but not to a level that matters for my application).
I think a persistent pragma would be more appropriate, don't you think?
Greetings,
Dirk
On 7/5/05, Roger Binns <[EMAIL PROTECTED]> wrote:
> > Anything about sqlite_master table information I guess, or maybe I missed
> > it?
>
> http://www.sqlite.org/faq.html#q9
>
Ok, I missed the faqs. Thanks.
> I prefer using the pragmas:
>
> http://www.sqlite.org/pragma.html#schema
>
> Roger
Anything about sqlite_master table information I guess, or maybe I missed it?
http://www.sqlite.org/faq.html#q9
I prefer using the pragmas:
http://www.sqlite.org/pragma.html#schema
Roger
18 matches
Mail list logo
