Tim,
>Queries using GLOB do use the index on the column in question (i.e.
>optimization is attempted)
>Queries using LIKE do not use that index if the LIKE operator has been
>overridden.
Sorry but GLOB doesn't use an index either if LIKE/GLOB has been
overloaded. This is consistent with the
On 26 Apr 2010, at 9:30pm, Forrie wrote:
> We are using Redhat, which tends to lag behind in some versioning --
> we want to use the latest version of Subversion 1.6.x, which in turn
> requires a newer version of Sqlite -- RHEL has an older version
> present, which in turn is a dependency for a
That sounds about right, but you should ensure that LD_LIBRARY_PATH is set
to reflect the appropriate sqlite lib folder each time you run something
that requires this, eg, your latest subversion install.
Goodluck,
Paul
On Mon, Apr 26, 2010 at 1:30 PM, Forrie wrote:
> We are
We are using Redhat, which tends to lag behind in some versioning --
we want to use the latest version of Subversion 1.6.x, which in turn
requires a newer version of Sqlite -- RHEL has an older version
present, which in turn is a dependency for a slew of other subsystems
(so uninstalling it would
thank you for valuable comments.
> At least, there should be a pragma or clause similar to the "deferred"
> clause available for foreign keys, causing uniqueness/existence/custom
> constraints to be checked only after FK (=trigger) action. With such
> feature available, we wouldn't have to
Just to complete the thread, I decided for the following:
SELECT substr(normalized,1,1) AS letter, COUNT(*) from entry group by
letter order by letter;
Thank you ALL!
2010/4/26 Alberto Simões :
> Hello
>
> Thank you all for the answers.
>
> On Mon, Apr 26, 2010 at 12:59 PM,
Hello
Thank you all for the answers.
On Mon, Apr 26, 2010 at 12:59 PM, Black, Michael (IS)
wrote:
> When you say "running on the fly" do you mean running from an sqlite3 command
> prompt?
I mean somebody will query it and will be waiting for the answer.
> Or are you
@jason
I'd like to follow-up Igor's and Michael's suggestion (see their referred-to
messages below).
How about that:
a) You do a dump of your database table containing the values bob,
jean-batiste, ...
a1) select a file for your dump:
sqlite> .output FILENAME
a2) Dump the database in an SQL
Edit: I meant to type "Firefox" not Firebird.
___
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
I am not quite sure what it is, and why it is, that you are doubting,
Jean-Christophe.
Queries using GLOB do use the index on the column in question (i.e.
optimization is attempted)
Queries using LIKE do not use that index if the LIKE operator has been
overridden.
You could confirm this claim
Yes currently it depends on the order. Should be checking if it can be
avoided.
The issue has been resolved by the method you've suggested (INSERT INTO
new_table (col_1, col_3)
SELECT col_1, col_2 FROM old_table;)
Thanks to everyone!!
I am looking for how to get total no.of columns even if the
> I just have some doubts on the licensing issues of SQLite.
>
>1. Being open-source, is my company liable to post back
> changes/modifications to
> SQLite? What are the licensing terms & conditions?
>2. As our present development is on a Linux variant, are there any
>
From: "Simon Slavin"
Sent: Monday, April 26, 2010 2:31 PM
> I don't know the answer to this question, but I have considered it in one
> of my
> programs. It simply issues a "PRAGMA recursive_triggers = 'on'", then
> does a
> "PRAGMA recursive_triggers" and looks to see what it gets back.
At 14:31 26/04/2010, you wrote:
>If the implementation of SQLite you are using overrides the LIKE operator
>(as more than a few do), then SQLite will not make use of an index on the
>column in question. Use the GLOB operator instead.
I doubt it. GLOB is absolutely nothing more or less than an
Yes. If the OP's [normword] column contains proper nouns, he must normalize
to lower case in order to get accurate results from GLOB.
Or, if his lexicon contains proper nouns in upper case and normal nouns in
lower case, then he could always leave the case intact and use GLOB to get a
count of
Tim Romano wrote:
> If the implementation of SQLite you are using overrides the LIKE operator
> (as more than a few do), then SQLite will not make use of an index on the
> column in question. Use the GLOB operator instead.
>
> For example, I have a lexicon containing 263,000 words:
>
> select
On 26 Apr 2010, at 11:09am, Andy Gibbs wrote:
> I notice in the fossil repository that Sqlite is now moving towards version
> 3.7.0. According to the pagehttp://www.sqlite.org/news.html#2009_sep_11, it
> is anticipated that recursive triggers will be enabled by default from
> version 3.7.0
If the implementation of SQLite you are using overrides the LIKE operator
(as more than a few do), then SQLite will not make use of an index on the
column in question. Use the GLOB operator instead.
For example, I have a lexicon containing 263,000 words:
select count(*) from lexicon where
On 26 Apr 2010, at 1:04pm, Michal Seliga wrote:
> i had similar problems and it was caused by microsoft office
> it didn't used ordinary dash but some strange character with different
> ascii code - so search based on it always failed
> i had to convert these strange dashes to ordinary ones to
Hi,
I notice in the fossil repository that Sqlite is now moving towards version
3.7.0. According to the page http://www.sqlite.org/news.html#2009_sep_11, it
is anticipated that recursive triggers will be enabled by default from version
3.7.0 (cf also
i had similar problems and it was caused by microsoft office
it didn't used ordinary dash but some strange character with different
ascii code - so search based on it always failed
i had to convert these strange dashes to ordinary ones to make it work
try, maybe this is also your case
When you say "running on the fly" do you mean running from an sqlite3 command
prompt?
Or are you doing this in some other programming language?
Why in the world would you use a database to do this?
Michael D. Black
Senior Scientist
Northrop Grumman Mission Systems
First off confirm it's not a bug with sqlite2:
sqlite> create table Groups (name varchar(10));
sqlite> insert into Groups values('bob');
sqlite> insert into Groups values('jean-baptiste');
sqlite> select * from Groups where name='jean-baptiste';
jean-baptiste
If you don't get a results this
23 matches
Mail list logo