niXforums Forum Index
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   PreferencesPreferences   Log in to check your private messagesLog in to check your private messages   Log inLog in 
·  nixdoc.net ·  man pages ·  Linux HOWTOs ·  FreeBSD Tips ·  Forums
navigation Forum index » Databases » MySQL
err-report help me
Post new topic   Reply to topic Page 67 of 67 [996 Posts] View previous topic :: View next topic
Goto page:  Previous  1, 2, 3, ..., 65, 66, 67
Author Message
Peter Lauri
*nix forums beginner


Joined: 25 Nov 2005
Posts: 40

PostPosted: Thu Jul 20, 2006 10:51 am    Post subject: RE: FULL TEXT and Asian languages Reply with quote

That is what I am doing right now, but it is not that fast if this system
would grow, and also it is not "ranking" the searches.

Right now I do something like this:

$searchwords = explode(" ", $searchstring);
foreach($searchwords AS $value) {
$Query.= "OR lajlaj LIKE '%$value%'"
}

If there are many search words, the OR will grow a bit, and OR are not that
fast as I read somewhere.

/Peter

-----Original Message-----
From: JC [mailto:hiep@ee.ucr.edu]
Sent: Thursday, July 20, 2006 10:46 PM
To: Peter Lauri
Cc: mysql@lists.mysql.com
Subject: Re: FULL TEXT and Asian languages

don't know about indexing, but try to search: LIKE '%sentences%'

JC

On Thu, 20 Jul 2006, Peter Lauri wrote:

Quote:
Best group member,

I have a problem. I was going to use FULL TEXT search for my Thai client.
It
is working smooth with English text and wordings, the indexing and search
works fine.

The problem with Thai text is that words are not separated with a white
space as in English and other languages. I think this screws up the
indexing, and complete sentences are classed as a word. Assume Thai
characters:

Thisisasentenceinthai. ButIcannotsearchforsentenceinthatsearch.

I want to search for "sentence", but can not. How can this be done? And
will
the indexing ever work?

Best regards,

Peter Lauri









--


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org
Back to top
Peter Lauri
*nix forums beginner


Joined: 25 Nov 2005
Posts: 40

PostPosted: Thu Jul 20, 2006 10:53 am    Post subject: RE: FULL TEXT and Asian languages Reply with quote

Why can the Thai and Chinese not use regular sentences and word delimiter Smile
So I have to stick to my LIKE thing, just to erase the FULL TEXT index I
assume.

-----Original Message-----
From: Neculai Macarie [mailto:mack@eaccelera.ro]
Sent: Thursday, July 20, 2006 10:50 PM
To: mysql@lists.mysql.com
Subject: Re: FULL TEXT and Asian languages

Peter Lauri wrote:
Quote:
Best group member,

I have a problem. I was going to use FULL TEXT search for my Thai
client. It is working smooth with English text and wordings, the
indexing and search works fine.


"The FULLTEXT parser determines where words start and end by looking for
certain delimiter characters; for example, ' ' (space), ',' (comma), and '.'
(period). If words are not separated by delimiters (as in, for example,
Chinese), the FULLTEXT parser cannot determine where a word begins or ends.
To be able to add words or other indexed terms in such languages to a
FULLTEXT index, you must preprocess them so that they are separated by some
arbitrary delimiter such as '"'."

http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html

--
<mack />


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=lists@dwsasia.com


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org
Back to top
Dominik Klein
*nix forums beginner


Joined: 15 Mar 2006
Posts: 35

PostPosted: Thu Jul 20, 2006 11:00 am    Post subject: Re: Problems with synchronisation master -> slave Reply with quote

Hi Thomas

Quote:
I try to configure replication from master to one slave for a database
with various table types (InnoDB, MyISAM) without stopping the master.

Therefore I make a mysqldump on the slave from master with this options:
mysqldump
-h master-db \
-udummyuser \
-pdummypass \
-v \
--all-databases \
--disable-keys \
--quick \
--single-transaction \

Single-transaction only affects innodb tables.

As single-transaction sets --skip-lock-tables automatically,
MyISAM-tables are not locked during the dump.
I think this is why you get the "row exists already" problem.

I'd suggest dumping innodb data and myisam data separatly. One mysqldump
WITH single-transaction (for innodb) and one without.
This leaves the problem of data being inserted in the meantime, as
master position will vary.

No idea at hand right now :(

Quote:
--master-data \
backup.file

an read the dump to the slave with:
mysql \
-u dummyuser \
-pdummypass \
backup.file

When I take a look to the backup.file, I see a line like this:
CHANGE MASTER TO MASTER_LOG_FILE='webdb1-bin.000170',
MASTER_LOG_POS=151635461;
caused by the option "--master-data".

But when I start the slave, there are soon the error message, that the
replication process will insert new row to a table, where this row exists
already.

Next try was, to delete all data in slave and then start replication from
the master from the beginning on (master-bin.000001), because we haven't
deleted any binlogs on master. After some time there appears an error
message, that there was an unsuccessful insert to an table, which doesn't
exist. Also the schema/catalog for this new table doesn't exist.

The question is now, why the creation of the new schema/catalog and the
table wasn't logged in the binlogs, so that they are not created via
replication before some inserts/updates are processed on them.

Maybe someone disabled log-bin temporarily when creating the db/table
(for tests or whatever) and forgot about this when inserting data later.

Quote:
Are the
binlogs not consistent? By the way, the "problem tables" are of type
MyISAM.

"Problem tables" = binlogged, but non-existent tables?
or
"Problem tables" = "row exists problem"-tables?

Regards
Dominik

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org
Back to top
Hiep Nguyen
*nix forums beginner


Joined: 11 Aug 2005
Posts: 11

PostPosted: Thu Jul 20, 2006 3:45 pm    Post subject: Re: FULL TEXT and Asian languages Reply with quote

don't know about indexing, but try to search: LIKE '%sentences%'

JC

On Thu, 20 Jul 2006, Peter Lauri wrote:

Quote:
Best group member,

I have a problem. I was going to use FULL TEXT search for my Thai client. It
is working smooth with English text and wordings, the indexing and search
works fine.

The problem with Thai text is that words are not separated with a white
space as in English and other languages. I think this screws up the
indexing, and complete sentences are classed as a word. Assume Thai
characters:

Thisisasentenceinthai. ButIcannotsearchforsentenceinthatsearch.

I want to search for "sentence", but can not. How can this be done? And will
the indexing ever work?

Best regards,

Peter Lauri









--


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org
Back to top
Neculai Macarie
*nix forums beginner


Joined: 13 Feb 2005
Posts: 8

PostPosted: Thu Jul 20, 2006 3:49 pm    Post subject: Re: FULL TEXT and Asian languages Reply with quote

Peter Lauri wrote:
Quote:
Best group member,

I have a problem. I was going to use FULL TEXT search for my Thai
client. It is working smooth with English text and wordings, the
indexing and search works fine.


"The FULLTEXT parser determines where words start and end by looking for
certain delimiter characters; for example, ' ' (space), ',' (comma), and '.'
(period). If words are not separated by delimiters (as in, for example,
Chinese), the FULLTEXT parser cannot determine where a word begins or ends.
To be able to add words or other indexed terms in such languages to a
FULLTEXT index, you must preprocess them so that they are separated by some
arbitrary delimiter such as '"'."

http://dev.mysql.com/doc/refman/5.0/en/fulltext-search.html

--
<mack />


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org
Back to top
Visolve DB Team
*nix forums beginner


Joined: 21 Jul 2006
Posts: 3

PostPosted: Fri Jul 21, 2006 5:11 am    Post subject: Re: FULL TEXT and Asian languages Reply with quote

Hi Peter,

Definitely using OR will slow up the performance of FULL TEXT searching.
Instead of using OR, you can try using UNION statement.

Hope this will be a fix for your issue.

Thanks,
ViSolve MySQL Support Team.


----- Original Message -----
From: "Peter Lauri" <lists@dwsasia.com>
To: "'JC'" <hiep@ee.ucr.edu>
Cc: <mysql@lists.mysql.com>
Sent: Thursday, July 20, 2006 4:21 PM
Subject: RE: FULL TEXT and Asian languages


Quote:
That is what I am doing right now, but it is not that fast if this system
would grow, and also it is not "ranking" the searches.

Right now I do something like this:

$searchwords = explode(" ", $searchstring);
foreach($searchwords AS $value) {
$Query.= "OR lajlaj LIKE '%$value%'"
}

If there are many search words, the OR will grow a bit, and OR are not
that
fast as I read somewhere.

/Peter

-----Original Message-----
From: JC [mailto:hiep@ee.ucr.edu]
Sent: Thursday, July 20, 2006 10:46 PM
To: Peter Lauri
Cc: mysql@lists.mysql.com
Subject: Re: FULL TEXT and Asian languages

don't know about indexing, but try to search: LIKE '%sentences%'

JC

On Thu, 20 Jul 2006, Peter Lauri wrote:

Best group member,

I have a problem. I was going to use FULL TEXT search for my Thai client.
It
is working smooth with English text and wordings, the indexing and search
works fine.

The problem with Thai text is that words are not separated with a white
space as in English and other languages. I think this screws up the
indexing, and complete sentences are classed as a word. Assume Thai
characters:

Thisisasentenceinthai. ButIcannotsearchforsentenceinthatsearch.

I want to search for "sentence", but can not. How can this be done? And
will
the indexing ever work?

Best regards,

Peter Lauri









--


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
http://lists.mysql.com/mysql?unsub=mysql_support@visolve.com




--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.2/393 - Release Date: 7/19/2006




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql?unsub=gcdmg-mysql@m.gmane.org
Back to top
Google

Back to top
Display posts from previous:   
Post new topic   Reply to topic Page 67 of 67 [996 Posts] Goto page:  Previous  1, 2, 3, ..., 65, 66, 67
View previous topic :: View next topic
The time now is Sun Nov 23, 2008 1:24 pm | All times are GMT
navigation Forum index » Databases » MySQL
Jump to:  

Similar Topics
Topic Author Forum Replies Last Post
No new posts Success delivery report kennykilla Postfix 0 Wed Aug 29, 2007 9:06 am
No new posts Bug Report - Solaris 10 spell Richard B. Gilbert Solaris 0 Fri Jul 21, 2006 11:22 am
No new posts Work-needing packages report for Jul 21, 2006 wnpp@debian.org devel 0 Fri Jul 21, 2006 6:50 am
No new posts Work-needing packages report for Jul 14, 2006 wnpp@debian.org devel 0 Fri Jul 14, 2006 6:50 am
No new posts Work-needing packages report for Jul 7, 2006 wnpp@debian.org devel 0 Fri Jul 07, 2006 6:50 am

Mobile Phones | Remortgaging | Israel Perry | Loans | Mortgages
Copyright © 2004-2005 DeniX Solutions SRL
 
Other DeniX Solutions sites: Unix/Linux blog |  electronics forum |  medicine forum |  science forum | 
Privacy Policy


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 6.5239s ][ Queries: 16 (6.4187s) ][ GZIP on - Debug on ]