RE: Limitation of Full-Text indexing in MyISAM table?

2001-12-10 Thread Al Caponi

> > >
> > > > On Dec 10, Al Caponi wrote:
> > > > >
> > > > > But I keep getting the following error when I try to delete
> > some row:
> > > > >
> > > > > java.sql.SQLException: General error: Incorrect key file
> for table:
> > > > > 'mytable'. Try to repair it
> > > > >
> > > > > So far, I've figured out that the error is due to mixing
> > > > > VARCHAR and TEXT
> > > > > type in the FULLTEXT index but I dunno why is there a problem.
> > > > > Haven't found much in MySQL doc about that yet.
> > > >
> > > > No, mixing VARCHAR and TEXT is perfectly legal
> > > > (even fulltext search example in the manual does it).
> > >
> > > Yup, seen that... which makes me even more frustrated :(
> > >
> > > >
> > > > What version of MySQL are you using ?
> > >
> > > I'm using MySQL 3.23.39 on Win98SE with JSDK 1.3
> >
> > This one is old. (June 2001)
> > The bug you've hit was fixed in Jule.
> >
>
> Is it the 'UPDATE|DELETE) ...WHERE MATCH bugfix' in MySQL 3.23.45?
> I'm not performing a delete using a WHERE MATCH but on a BIGINT
> column type.
> Anyway, I'll upgrade my MySQL version and check it out.

Problem solved after upgrading 3.23.46a for Win98. Haven't used
UPDATE|DELETE) ...WHERE MATCH  yet...

Cheers!


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




RE: Limitation of Full-Text indexing in MyISAM table?

2001-12-10 Thread Al Caponi

Hi,

> > >
> > > Hi!
> > >
> > > On Dec 10, Al Caponi wrote:
> > > >
> > > > But I keep getting the following error when I try to delete
> some row:
> > > >
> > > > java.sql.SQLException: General error: Incorrect key file for table:
> > > > 'mytable'. Try to repair it
> > > >
> > > > So far, I've figured out that the error is due to mixing
> > > > VARCHAR and TEXT
> > > > type in the FULLTEXT index but I dunno why is there a problem.
> > > > Haven't found much in MySQL doc about that yet.
> > >
> > > No, mixing VARCHAR and TEXT is perfectly legal
> > > (even fulltext search example in the manual does it).
> >
> > Yup, seen that... which makes me even more frustrated :(
> >
> > >
> > > What version of MySQL are you using ?
> >
> > I'm using MySQL 3.23.39 on Win98SE with JSDK 1.3
>
> This one is old. (June 2001)
> The bug you've hit was fixed in Jule.
>

Is it the 'UPDATE|DELETE) ...WHERE MATCH bugfix' in MySQL 3.23.45?
I'm not performing a delete using a WHERE MATCH but on a BIGINT column type.
Anyway, I'll upgrade my MySQL version and check it out.
Thanx
Al


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Limitation of Full-Text indexing in MyISAM table?

2001-12-10 Thread Sergei Golubchik

Hi!

On Dec 10, Al Caponi wrote:
> Hi Sergei!
> Thanks for the reply! That was fast :)
> 
> > -Original Message-
> > From: Sergei Golubchik [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, December 10, 2001 10:48 PM
> > To: Al Caponi
> > Cc: MySQL Mailing List
> > Subject: Re: Limitation of Full-Text indexing in MyISAM table?
> >
> >
> > Hi!
> >
> > On Dec 10, Al Caponi wrote:
> > >
> > > But I keep getting the following error when I try to delete some row:
> > >
> > > java.sql.SQLException: General error: Incorrect key file for table:
> > > 'mytable'. Try to repair it
> > >
> > > So far, I've figured out that the error is due to mixing
> > > VARCHAR and TEXT
> > > type in the FULLTEXT index but I dunno why is there a problem.
> > > Haven't found much in MySQL doc about that yet.
> >
> > No, mixing VARCHAR and TEXT is perfectly legal
> > (even fulltext search example in the manual does it).
> 
> Yup, seen that... which makes me even more frustrated :(
> 
> >
> > What version of MySQL are you using ?
> 
> I'm using MySQL 3.23.39 on Win98SE with JSDK 1.3

This one is old. (June 2001)
The bug you've hit was fixed in Jule. 
 
Regards,
Sergei

-- 
MySQL Development Team
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Osnabrueck, Germany
   <___/

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




RE: Limitation of Full-Text indexing in MyISAM table?

2001-12-10 Thread Al Caponi

Hi Sergei!
Thanks for the reply! That was fast :)

> -Original Message-
> From: Sergei Golubchik [mailto:[EMAIL PROTECTED]]
> Sent: Monday, December 10, 2001 10:48 PM
> To: Al Caponi
> Cc: MySQL Mailing List
> Subject: Re: Limitation of Full-Text indexing in MyISAM table?
>
>
> Hi!
>
> On Dec 10, Al Caponi wrote:
> > Hi all,
> > Is there any limitation in creating full-text indexes on MyISAM tables?
> > Currently, I have a table like this:
> > CREATE TABLE IF NOT EXISTS mytable (
> > UId BIGINT(20) NOT NULL AUTO_INCREMENT,
> > Title VARCHAR(255) NOT NULL,
> > Field1 TEXT,
> > Field2 TEXT,
> > Field3 VARCHAR(255),
> > Field4 TEXT,
> > Field5 TEXT,
> > Field6 VARCHAR(50),
> > Field7 VARCHAR(50),
> > Field8 VARCHAR(50),
> > Field9 TIMESTAMP NOT NULL,
> > Field10 TIMESTAMP NOT NULL,
> > PRIMARY KEY(UId),
> > INDEX article_idx1(Field6),
> > INDEX article_idx2(Field7),
> > INDEX article_idx3(Field8),
> > FULLTEXT article_idx4(Field1, Field2, Field3, Field4,
> Field5, Field6,
> > Field7, Field8)
> > ) TYPE=MyISAM;
> >
> > But I keep getting the following error when I try to delete some row:
> >
> > java.sql.SQLException: General error: Incorrect key file for table:
> > 'mytable'. Try to repair it
> >
> > So far, I've figured out that the error is due to mixing
> VARCHAR and TEXT
> > type in the FULLTEXT index but I dunno why is there a problem.
> Haven't found
> > much in MySQL doc about that yet.
>
> No, mixing VARCHAR and TEXT is perfectly legal
> (even fulltext search example in the manual does it).

Yup, seen that... which makes me even more frustrated :(

>
> What version of MySQL are you using ?

I'm using MySQL 3.23.39 on Win98SE with JSDK 1.3

> Can you create a testcase for that ?

I'm not too sure of how to go about creating that... Do you mean the test
code or just a rough idea of the testing?

Roughly, I'm just inserting a record and deleting it based on the UId field.

Regards,
Al


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Re: Limitation of Full-Text indexing in MyISAM table?

2001-12-10 Thread Sergei Golubchik

Hi!

On Dec 10, Al Caponi wrote:
> Hi all,
> Is there any limitation in creating full-text indexes on MyISAM tables?
> Currently, I have a table like this:
> CREATE TABLE IF NOT EXISTS mytable (
>   UId BIGINT(20) NOT NULL AUTO_INCREMENT,
>   Title VARCHAR(255) NOT NULL,
>   Field1 TEXT,
>   Field2 TEXT,
>   Field3 VARCHAR(255),
>   Field4 TEXT,
>   Field5 TEXT,
>   Field6 VARCHAR(50),
>   Field7 VARCHAR(50),
>   Field8 VARCHAR(50),
>   Field9 TIMESTAMP NOT NULL,
>   Field10 TIMESTAMP NOT NULL,
>   PRIMARY KEY(UId),
>   INDEX article_idx1(Field6),
>   INDEX article_idx2(Field7),
>   INDEX article_idx3(Field8),
>   FULLTEXT article_idx4(Field1, Field2, Field3, Field4, Field5, Field6,
> Field7, Field8)
> ) TYPE=MyISAM;
> 
> But I keep getting the following error when I try to delete some row:
> 
> java.sql.SQLException: General error: Incorrect key file for table:
> 'mytable'. Try to repair it
> 
> So far, I've figured out that the error is due to mixing VARCHAR and TEXT
> type in the FULLTEXT index but I dunno why is there a problem. Haven't found
> much in MySQL doc about that yet.

No, mixing VARCHAR and TEXT is perfectly legal
(even fulltext search example in the manual does it).

What version of MySQL are you using ?
Can you create a testcase for that ?

> Is the problem more on the Java side?

I doubt it.

Regards,
Sergei

-- 
MySQL Development Team
   __  ___ ___   __
  /  |/  /_ __/ __/ __ \/ /   Sergei Golubchik <[EMAIL PROTECTED]>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Osnabrueck, Germany
   <___/

-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php




Limitation of Full-Text indexing in MyISAM table?

2001-12-10 Thread Al Caponi

Hi all,
Is there any limitation in creating full-text indexes on MyISAM tables?
Currently, I have a table like this:
CREATE TABLE IF NOT EXISTS mytable (
UId BIGINT(20) NOT NULL AUTO_INCREMENT,
Title VARCHAR(255) NOT NULL,
Field1 TEXT,
Field2 TEXT,
Field3 VARCHAR(255),
Field4 TEXT,
Field5 TEXT,
Field6 VARCHAR(50),
Field7 VARCHAR(50),
Field8 VARCHAR(50),
Field9 TIMESTAMP NOT NULL,
Field10 TIMESTAMP NOT NULL,
PRIMARY KEY(UId),
INDEX article_idx1(Field6),
INDEX article_idx2(Field7),
INDEX article_idx3(Field8),
FULLTEXT article_idx4(Field1, Field2, Field3, Field4, Field5, Field6,
Field7, Field8)
) TYPE=MyISAM;

But I keep getting the following error when I try to delete some row:

java.sql.SQLException: General error: Incorrect key file for table:
'mytable'. Try to repair it

So far, I've figured out that the error is due to mixing VARCHAR and TEXT
type in the FULLTEXT index but I dunno why is there a problem. Haven't found
much in MySQL doc about that yet.
Is the problem more on the Java side?

Could anyone suggest any solution or direct me to some resources? (Other
than converting all my fields to TEXT :))

Many THANKS!!!

Al


_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com


-
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/   (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php