Hi!
On Mar 01, William Au wrote:
> Sergei, but this is a phrase search. The original query is:
>
> match (keywords) against ('"16-bit Touch"' IN BOOLEAN MODE)
>
> So shouldn't all words that are actually searched on be present
> in a particular order?
Ok, sorry.
If the original query is '"16-b
Sergei, but this is a phrase search. The original query is:
match (keywords) against ('"16-bit Touch"' IN BOOLEAN MODE)
So shouldn't all words that are actually searched on be present
in a particular order?
Bill
Sergei Golubchik wrote:
Hi!
On Feb 27, Haitao Jiang wrote:
Thanks! That was wh
Hi!
On Feb 27, Haitao Jiang wrote:
>
> Thanks! That was what I guessed. But how to explain
> "16-bit Touch" doesn't match records with "32-bit
> Touch" in the keywords? It just returned all the
> records with "16-bit Touch", i.e. "16-bit" seems does
> count.
Because the presense of "16-bit" subs
Thanks! That was what I guessed. But how to explain
"16-bit Touch" doesn't match records with "32-bit
Touch" in the keywords? It just returned all the
records with "16-bit Touch", i.e. "16-bit" seems does
count.
Thanks again!
Haitao
--- Michael Stassen <[EMAIL PROTECTED]>
wrote:
> It's expected
It's expected behavior, not a bug.
"16-bit Touch" is parsed as "16", "bit" and "touch". The first two are
ignored because they are too short. So, this searches for rows with
"touch", then selects the ones which contain your phrase.
"16-bit" contains no words to search for, so it returns nothi
Could anyone explain why
match (keywords) against ('"16-bit Touch"' IN BOOLEAN
MODE)
returns results, but not
match (keywords) against ('"16-bit"' IN BOOLEAN MODE)?
Is it a known bug?
Thanks a lot!
Haitao
__
Do you Yahoo!?
Get better spam protection with Y
Version: MySQL 4.0.11-gamma-nt
OS: Windows NT4 Server
I have a test table like this:
CREATE TABLE test (
created date NOT NULL default '-00-00',
duration smallint(5) unsigned NOT NULL default '0'
) TYPE=MyISAM;
INSERT INTO test VALUES("2003-01-01", "365");
INSERT INTO test VALUES("2003-0
OK,
I found out, why the table grows that extraordinary.
After
'CREATE TABLE new_1 SELECT * FROM output_1';
All columns of new_1 are CHAR(255) instead of VARCHAR(255) like in output_1
( see below).
Now my simple questions are:
1. Why , I saw something about silent changes in the docs,
Use BIGINT
use altertable ...that will take a week
Russell Griechen
- Original Message -
From: "Franz, Fa. PostDirekt MA" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, February 24, 2003 2:35 AM
Subject: Strange BUG? with a working table
> Dear Ladi
Compare tables with :
=show create table t1;
=show create table t2; Check table type.
Or use dump command from shell:
shell>mysqldump -pPassword --user=username db_name t1 > t1.sql
mysql>rename table t1 to t2;
shell>mysql -pPassword --user=username t1.sql > db_name
Or try to set MIN_ROWS
Hi Chiu,
>It seems that you have reached the 2G file limit with many Linux system. I
>am not familiar with SuSe. As I know, you may try to use raid option. You
>may refer to MySQL doc. on 'create' for details.
Yes I know, that I can just manage files to 2 GB.
The question was, why is the new ta
It seems that you have reached the 2G file limit with many Linux system. I
am not familiar with SuSe. As I know, you may try to use raid option. You
may refer to MySQL doc. on 'create' for details.
KH
> Dear Ladies and Sirs,
>
> I have a problem to create a tables duplicate with:
>
> CREATE
Dear Ladies and Sirs,
I have a problem to create a tables duplicate with:
CREATE TABLE new_1 SELECT * FROM output_1;
The table output_1 has this structure:
Field TypeNullKey
af_1int(11) YES MUL
af_3varchar(255)YES
I had this problem to but was never able to find what was causing it. The
way I got around it was by doing execute statements like:
connection.execute("INSERT INTO .")
That way I avoided VB handling the updates and it worked. But since Josh
pointed this little problems "solution" out I might g
Tom -
I'll address what I can
I had the same problem with fields being truncated on direct connections (the
problem does not manifest on ODBC table attaches in Access).
IIRC, the way to "solve" this problem is to make sure the "optimize columns
widths" (option 1) in the ODBC properties.
I've been pounding my head against a wall for the last couple of days trying
to make a "simple" program work (to then use as the basis for future
programs, etc. -- in other words, "I'm still just learning this stuff") I'd
really like to "point the finger" at Microsoft & visual basic, but I've bee
Hello Michael,
Thursday, February 08, 2001, 1:58:24 AM, you wrote:
Peter>> I've done mysqladmin "flush logs" and then copied the .frm and .db
Peter>> files into other database directory - and the bug was unable to be
Peter>> repaired.
MW> I assume you mean 'unable to be repeated' ?
Yes of co
Hi!
> "Peter" == Peter Zaitsev <[EMAIL PROTECTED]> writes:
Peter> Hello mysql,
Peter> mysql 3.23.32 + BDB 3.2.3h
mysql> select * from layers_la00.g03last_hit;
Peter> +++-+++
Peter> | updated| counter_id | stat_id |
Hello Miguel,
Wednesday, February 07, 2001, 5:52:50 AM, you wrote:
MAS> I have made the following table on Win2000 machine:
C:\mysql\bin>>mysql
MAS> Welcome to the MySQL monitor. Commands end with ; or \g.
MAS> Your MySQL connection id is 3 to server version: 3.23.30-gamma
MAS> Type 'help;'
At 11:50 06/02/2001, Peter Zaitsev wrote:
Hi!
I have made the following table on Win2000 machine:
C:\mysql\bin>mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3 to server version: 3.23.30-gamma
Type 'help;' or '\h' for help. Type '\c' to clear the buf
Peter Zaitsev writes:
> Hello mysql,
>
> mysql 3.23.32 + BDB 3.2.3h
>
>
> mysql> select * from layers_la00.g03last_hit;
> +++-+++
> | updated| counter_id | stat_id | lasthit_ts | lasthit_id |
> +
Hello mysql,
mysql 3.23.32 + BDB 3.2.3h
mysql> select * from layers_la00.g03last_hit;
+++-+++
| updated| counter_id | stat_id | lasthit_ts | lasthit_id |
+++-++
22 matches
Mail list logo