Wednesday, from David Axmark:
> > Your other point about exact vs. approximate answers is unclear, I expect
> > that Google's answers are exact for their currently available indexes at any
> > given time. But even if they are approximate, I'd be happy with that too.
> > The scoring on a FULLTEXT
Wednesday, from Mike Wexler:
> I don't think that would be appropriate. My example, is our site (tias.com) has
> lots of antiques and collectibles. One popular categories is jewelry. If
> somebody does a search for "gold jewelry" and the search engine interprets this
> as anything that mentions go
Hi, I also will explain how we made FTS "fast". (sorry for my bad english)
First some DATA: The table which has to be indexed has ~60 entries.
There are articles inside it, which are in average 3-4 kb each (which says
nothing!) with about 300 words each (this number is very important!).
Thi
Yesterday, from savaidis:
> The obious question is: (before I test it)
> This is concatenation to $query that is a string type, no?
Yea. The following works either:
mysql_query("create bla".
"bla".
"bla
bla blabla
".
"bla"
."bla"
);
> So the limit isn't
Tuesday, from Matt Rudderham:
> Hello, I have two tables in my database as such:
>
> CREATE TABLE `skill_names` (
> `id` bigint(20) NOT NULL auto_increment,
> `name` varchar(30) NOT NULL default '',
> PRIMARY KEY (`id`)
> );
>
> CREATE TABLE `skills` (
> `skills_id` int(11) NOT NULL aut
Yesterday, from Brian DeFeyter:
> Has anyone made a suggestion or thought about ways to distribute
> databases which focus on fulltext indexes?
>
> fulltext indexes do a good job of indexing a moderate amount of data,
> but when you get a lot of data to be indexed, the queries slow down
> signifi
Yesterday, from Nathan:
> Since PHP ignores whitespace, I think this is also acceptable:
PHP doesn't ignore whitespace in a quote. But your code is of course
correct.
> $query = "CREATE TABLE query
> tabledef for col a,
> tabledef for col b,
> lots more table defs,
> .
> welcome t
Yesterday, from Brian DeFeyter:
> Has anyone made a suggestion or thought about ways to distribute
> databases which focus on fulltext indexes?
>
> fulltext indexes do a good job of indexing a moderate amount of data,
> but when you get a lot of data to be indexed, the queries slow down
> signifi
Tuesday, from Matt Rudderham:
> Hello, I have two tables in my database as such:
>
> CREATE TABLE `skill_names` (
> `id` bigint(20) NOT NULL auto_increment,
> `name` varchar(30) NOT NULL default '',
> PRIMARY KEY (`id`)
> );
>
> CREATE TABLE `skills` (
> `skills_id` int(11) NOT NULL aut
Yesterday, from Nathan:
> Since PHP ignores whitespace, I think this is also acceptable:
PHP doesn't ignore whitespace in a quote. But your code is of course
correct.
> $query = "CREATE TABLE query
> tabledef for col a,
> tabledef for col b,
> lots more table defs,
> .
> welcome t
Yesterday, from savaidis:
> The obious question is: (before I test it)
> This is concatenation to $query that is a string type, no?
Yea. The following works either:
mysql_query("create bla".
"bla".
"bla
bla blabla
".
"bla"
."bla"
);
> So the limit isn't
I found out, that the fulltext engine is misbehaving with less than 5
entries. Seems to me, that this is exactly the same case...
Perhaps a flush inside the engine or so isn't made with such less entries?
The bug is also in 3.23 gamma.
Workaround: Enter more rows to fix it. :)
I send this bug
12 matches
Mail list logo
