Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-12-09 Thread AmirBehzad Eslami
Behdad Esfahbod wrote: > That's the tricky part, or where the runtime-hell comes in. What > I did was to write a small java program based on the samples in > Lucene to connect to my database and feed the data into Lucene. > At search time, I have another little Java program that takes the > q

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-12-04 Thread Behdad Esfahbod
On Wed, 30 Nov 2005, AmirBehzad Eslami wrote: > Dear Behdad, > > On 25 Nov 2005, you wrote: > > > Another options is to get yourself a real search engine, like > > Apache Lucene. I've written my experience using that here: > > > > http://mces.blogspot.com/2005/04/on-lucene-and-its-decency.html

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-30 Thread AmirBehzad Eslami
Dear Behdad,   On 25 Nov 2005, you wrote: > Another options is to get yourself a real search engine, like> Apache Lucene. I've written my experience using that here: >> http://mces.blogspot.com/2005/04/on-lucene-and-its-decency.htmlYou always offer the most brilliant solutions!!Unfortunately, I

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-30 Thread AmirBehzad Eslami
Dear Ehsan, On Nov 28, 2005, you wrote:   > I've actually implemented this approach in a project.  I have not yet published the > code, but if you want, I can make it available under the GPL. Yes! I would appreciate it.Thank you very much for your kindness. Behzad Yahoo! Music Unlimited -

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-28 Thread Ehsan Akhgari
  Dear Ehsan,You suggested a creative solution. Thank you.My application, consists of a database, and two user-interfaces.The first UI is used for data entry,where I parse a given XML file, extract and "Romanize" itsdata - based on a "Persian-Roman Conversion Map" -and then ins

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-27 Thread AmirBehzad Eslami
Mohsen wrote:> But himself solved his problem. > with : mysql_query("SET NAMES utf8"); > Even 4.0.xWrong. I decided to prepare two different versions for my software: - A MySQL 4.0-friendly version using Romanizing method (Hats off to you, Ehsan) - A MySQL 4.1-compatible version.

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-27 Thread Mohsen Pahlevanzadeh
[EMAIL PROTECTED] wrote: AmirBehzad Eslami <[EMAIL PROTECTED]> wrote on 24/11/2005 17:48:29: Dear list, I'm considering programming a simple "Search Engine" for a website, to find Arabic/Persian data within a MySQL database. This database contains a huge amount of data, encoded with

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-27 Thread Alec . Cawley
AmirBehzad Eslami <[EMAIL PROTECTED]> wrote on 24/11/2005 17:48:29: > Dear list, > > I'm considering programming a simple "Search Engine" for a website, > to find Arabic/Persian data within a MySQL database. > This database contains a huge amount of data, encoded with Unicode(UTF-8). > >

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-25 Thread AmirBehzad Eslami
Ehsan Akhgari wrote:> Another solution is make the db believe your text is English. > This could be done by "romanizing" the text before inserting it to the db, > and converting it back to Unicode after reading it from the db and before > displaying it to the user.  This can be done by

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-25 Thread AmirBehzad Eslami
On Nov 24, 2005, Medi Montaseri wrote:> One solution would be to augment a DB capability > at the application level. That is instead of the search > or select qualified by a SQL where clause, simply get > everything (select *) and then let the application filter > what you want. Then when y

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-24 Thread Behdad Esfahbod
On Fri, 25 Nov 2005, Ehsan Akhgari wrote: > > One solution would be to augment a DB capability > at the application level. That is instead of the search > or select qualified by a SQL where clause, simply get > everything (select *) and then let the application filter > what you want. Th

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-24 Thread Ehsan Akhgari
  One solution would be to augment a DB capabilityat the application level. That is instead of the searchor select qualified by a SQL where clause, simply geteverything (select *) and then let the application filterwhat you want. Then when your given DB providesthat operation by i

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-24 Thread Medi Montaseri
One solution would be to augment a DB capability at the application level. That is instead of the search or select qualified by a SQL where clause, simply get everything (select *) and then let the application filter what you want. Then when your given DB provides that operation by itself, simplify

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-24 Thread Behnam Esfahbod
AmirBehzad Eslami wrote: 2) Find another Web Hosting Company with PHP and MySQL 4.1 support. Would you (or anyone else in the list) recommend a reliable Web Hosting Company with such services?! You may like to see www.1and1.com. It's been our web hosting for 2 years now. -- ' '

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-24 Thread AmirBehzad Eslami
Mohsen wrote: > Please use MySQL 4.1 or higher.Dear Mohsen,Nice to e-meet(!) you here, at PersianComputing mailing list!Thanks for your advice. I just heared the same message from MySQL geeks at [EMAIL PROTECTED]I already know that MySQL 4.1 supports Unicode[1], and I can install

Re: MySQL 4.0, FULL-TEXT Indexing and Search Arabic Data, Unicode

2005-11-24 Thread Mohsen Pahlevanzadeh
AmirBehzad Eslami wrote: Dear list, I'm considering programming a simple "Search Engine" for a website, to find Arabic/Persian data within a MySQL database. This database contains a huge amount of data, encoded with Unicode (UTF-8). The big deal is to ** reduce the response time ** to end-u