Brent Baisley wrote:
The other thing to consider is the 50% rule. If more than 50% of the
records match, the search is consider irrelevant and no records are
returned. So if you have 120 records and 61 have DB2 in them, you won't
get a result set.
But the 50% rule is overridden when the search
I have a table with the following:
CREATE TABLE foo (
...
description text,
...
FULLTEXT INDEX (description),
...
);
select count(*) from foo where description like '%db2%';
returns 61 rows. Checking them confirms that the word db2 exists as a
standalone word separated either by punctuation or
Richard Davey wrote:
Hello Shane,
Wednesday, March 31, 2004, 5:43:10 AM, you wrote:
SA using MATCH(description) AGAINST('+db2' IN BOOLEAN MODE) returns no results.
SA Is this expected behaviour? If so, is there a way to circumvent it?
By default, the full text indexing engine doesn't include
I've read through the boolean mode fulltext docs, and they address all
my questions well except how searches containing exact phrases are
handled when there is more than one. I believe the following will work
as I expect, but was wondering if anyone can confirm it for me:
Given the following
At 09:24 PM 11/10/2003, Leo wrote:
notice the _and_ ?
*grin*
good point. I guess my reply (which I found out later was unnecessary since
the question had already been answered) would have been better stated had I
just pointed out the distinct keyword rather than constructing a sample
query. :)
At 07:45 PM 11/7/2003, Jonathan Terhorst wrote:
snip
One way I have found to implement this is
SELECT Table1.id from Table1 JOIN Features USING(id) WHERE
Features.FeatureCode='A01' OR Features.FeatureCode='B02' GROUP BY Table1.id
HAVING COUNT(*)=2;
e.g. counting the duplications of id and
I've searched the archives and was unable to find anything that seemed
pertinent.
Earlier today I had to stop and start mysql. When I issued mysqladmin
shutdown, however, the process did not die cleanly (reason unknown), and I
ended up having to kill -9 mysqld and mysqld_safe.
When the DB
Running 4.0.15a. The second select's FOUND_ROWS() returns the wrong number of rows.
To test yourself:
create database test1234;
\r test1234
create table test (id int, primary key (id));
insert into test values (1), (2), (3), (4), (5);
select SQL_CALC_FOUND_ROWS * from test where id 3 limit 0,
, changing
either setting would require a rebuild of the FT index(es), but then, so
does FT_MIN_WORD_LENGTH...
TIA
--
Shane Allen [EMAIL PROTECTED]
http://www.emphasys.net
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/[EMAIL
We're considering switching to InnoDB tables for a couple of tables in
our database where we need transactions. We're complete newbies with
reference to innodb, although we are seasoned veterans with regards to
MySQL/MyISAM and general concepts.
We have come up with a couple questions that we
I've actually noticed this in the past several releases; I apologize for
not mentioning it sooner.
I run:
BUILD/compile-pentium --with-other-libc=/usr/local/mysql-glibc-2.2.5
--prefix=/usr/local --with-extra-charsets=none --without-innodb --without-isam
and part-way through, it fails.
Description
This may be by design, but I figured I'd bring it up because it caused
less-than-desirable behaviour for me. I executed an alter table query, designed to
change the length of a fixed width char field to 128 from 255. The alter occured fine,
with no problems, except that there were
How about this:
mysql CREATE TABLE tablename (value1 int(10) AUTO_INCREMENT, value2 timestamp(14),
PRIMARY KEY (value1));
Query OK, 0 rows affected (0.00 sec)
mysql INSERT SQL_RETURN_INSERT_ID INTO tablename (value1, value2) VALUES (0, NOW());
+-+
| INSERT_ID() |
+-+
|
This is a repost of my previous message with a new and improved title
that will hopefully catch more eyes and generate a response. :)
We have two users, lets call them test and test2.
When we log in as test from our front end web servers, we can execute queries and
they replicate.
When we
We have two users, lets call them test and test2.
When we log in as test from our front end web servers, we can execute queries and they
replicate.
When we log in as test from our back end db servers (say to run a cleanup script by
hand), the queries replicate.
When we log in as test2 from
exist but are not used (even if specified with use index(..)) ?!
Sounds like you should either:
ALTER TABLE telegramme ADD INDEX combined (to_id, owner_id);
or
SELECT * FROM telegramme WHERE to_id = 3157 UNION SELECT * FROM telegramme WHERE
owner_id = 3157;
HTH
--
Shane Allen [EMAIL PROTECTED
I am trying to build MySQL from a new clone of the bitkeeper repository, and am
running into some difficulty...
I am running Debian Woody, and am running unstable. Following are the relevant
utilities/versions installed on my system:
I haven't seen any traffic on this thread, so I figured I'd repost it
with a slightly more catchy subject. :)
Has anyone looked into this?
On Tue, Oct 08, 2002 at 09:12:13PM -0500, Shane Allen wrote:
Description:
See How-To-Repeat
How-To-Repeat:
I uploaded a copy of the tables
, listing_id, last_modified);
did not.
Fix:
Adding indexes (See How-To-Repeat)
Submitter-Id:
Originator: Shane Allen [EMAIL PROTECTED]
Organization: sell.com
MySQL support: none
Synopsis:
Severity:
Priority:
Category: mysql
Class:
Release: mysql-4.0.4-beta (Source distribution)
Server
statement, at least in the case of a MyISAM
table.
Thanks
--
Shane Allen [EMAIL PROTECTED]
interesting side-note: mutt's list-reply misses my send-hooks... :)
-
Before posting, please check:
http://www.mysql.com/manual.php
On Thu, Oct 03, 2002 at 06:39:26PM -0500, Shane Allen wrote:
We have a 4.0.4-beta master and slave.
The slaving process starts correctly, but randomly (and frequently) has
issues.
When the server starts, it will slave, but eventually will hit one of
two conditions:
- Duplicate key
On Fri, Oct 04, 2002 at 12:36:30PM -0700, David McInnis wrote:
Can someone please help me with the following? Normally I would do this
with a nested select, but since this is not available in MySQL I think I
need help.
Here is what I have: An order table with sales tax total and an
the slave to 4.0.3 fixed the instability AFAICT (it's only
been reverted for a brief period). The master has remained at 4.0.4
Let me know if you need further info.
Thanks
--
Shane Allen [EMAIL PROTECTED]
-
Before posting, please
)
);
insert into test1 values (1,'test');
insert into test1 values (2,'test');
insert into test2 values (1,'test');
insert into test2 values (2,'test');
select distinct * from test1 t1 left join test2 t2 on (t1.i1=t2.i1);
Fix:
None known
Submitter-Id: submitter ID
Originator:Shane Allen (shane
Apologies,
I thought I had done a decent search to see if anyone else had reported
it, but apparently my search skills are lacking, I see that it was fixed
in 4.0.4.
On Wed, Sep 25, 2002 at 11:34:07PM -0500, Shane Allen wrote:
Description:
selecting distinct when executing a left join
]
open-files-limit=8192
err-log=/usr/local/var/mysqld.err
--
Shane Allen [EMAIL PROTECTED]
sell.com : Buy Sell Anything
http://www.sell.com
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual
On Fri, Aug 02, 2002 at 10:59:18PM +0200, Georg Richter wrote:
On Friday, 2. August 2002 20:48, Shane Allen wrote:
I digress... at this point, the question that plagues me is: Is it normal
for MySQL to die under high load?
you have a lot of programs, which prefer to die under heavy load
config.log with regards to the gethost* function(s)
Thanks
On Sat, Jun 22, 2002 at 02:40:38AM -0500, Shane Allen wrote:
configure:12730: checking style of gethost* routines
configure:12773: gcc -c -O -DDBUG_OFF -O3 -felide-constructors -fno-exceptions
-fno-rtti
-fpermissive -I/usr/local/mysql
:15312: $? = 0
configure:15315: test -s conftest.o
configure:15318: $? = 0
configure:15328: result: glibc2
)
Regards,
Jocelyn
- Original Message -
From: Shane Allen [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Saturday, June 22, 2002 3:05 AM
Subject: Build errors with 3.23.51
[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/src/mysql-3.23.51'
make: *** [all-recursive-am] Error 2
root@dbmaster:/usr/local/src/mysql-3.23.51#
Let me know if I need to provide any further info.
TIA
--
Shane Allen [EMAIL PROTECTED
wondering
why the discrepancy?
--
Shane Allen [EMAIL PROTECTED]
sell.com : Buy Sell Anything
http://www.sell.com
-
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com
31 matches
Mail list logo