[pLog-svn] r4676 -plog/branches/lifetype-1.2/class/database/pdb/drivers

[Jon Daley]

 	That doesn't sound good.  I don't know what to do about the 
encoding blacklist problem with UTF-8 (unless we do it as a config option, 
though I do agree it seems kind of odd to have the config class shared 
over to the driver database, though the config class is a sort of 
low-level thing), but it seems like a worse idea to do our own full-text 
stuff - you could just keep using LIKE.

  On Sat, 3 Feb 2007, Mark Wu wrote:

> I will try to figure a list a put it into backlist.
>
> Another idea is implement our own full-text engine. But, it will double or
> triple our data base consumption. :(
>
> Take article_text for example, we can add another filed like
> aticle_text_for_fulltext, then we write our own word spliter:
>
> So, when we save the article_text, we will process the content with our own
> spliter and sve to aticle_text_for_fulltext, and we can use this field for
> fulltext search.
>
> I check the vBullitin (I forgot who told me this), they use this way to
> solve the fulltext search issue in CJK environment.
>
> Mark
>
>> -----Original Message-----
>> From: plog-svn-bounces at devel.lifetype.net
>> [mailto:plog-svn-bounces at devel.lifetype.net] On Behalf Of
>> Oscar Renalias
>> Sent: Saturday, February 03, 2007 7:30 AM
>> To: plog-svn at devel.lifetype.net
>> Subject: Re: [pLog-svn] r4676
>> -plog/branches/lifetype-1.2/class/database/pdb/drivers
>>
>> Right now the only way to turn it off is by "blacklisting"
>> your database character encoding in PDbMySQLDriver. And since
>> this is living at the database driver level and that has
>> nothing to do with the UI, I'm not sure that binding the
>> database driver class to the Config class is a good idea.
>>
>> How about an extra optional parameter in the
>> config.properties.php file? Would that be good enough?
>>
>> On 3 Feb 2007, at 01:26, Jon Daley wrote:
>>
>>>  	Can we have a configuration option to turn this on and
>> off as well?
>>>
>>> On Fri, 2 Feb 2007, oscar at devel.lifetype.net wrote:
>>>> Author: oscar
>>>> Date: 2007-02-02 17:54:59 -0500 (Fri, 02 Feb 2007) New
>> Revision: 4676
>>>>
>>>> Modified:
>>>>   plog/branches/lifetype-1.2/class/database/pdb/drivers/
>>>> pdbdriverbase.class.php
>>>>   plog/branches/lifetype-1.2/class/database/pdb/drivers/
>>>> pdbmysqldriver.class.php
>>>> Log:
>>>> Added driver-specific support for FULLTEXT indexes, so now
>> the driver
>>>> can tell the user classes whether fulltext queries are
>> supported or
>>>> not. Fulltext is disabled by default in the base driver
>> class but the
>>>> MySQL driver will first check the database character encoding to
>>>> determine whether FULLTEXT is supported or not. The method
>>>> PDbMySQLDriver::isFullTextSupported() holds an array with
>>>> "blacklisted" character sets that don't support FULLTEXT but it
>>>> currently is set to empty (meaning that FULLTEXT is
>> supported accross
>>>> all mysql character sets so I'm hoping that Mark or somebody more
>>>> familiar with this will help me fill in the array.
>>> _______________________________________________
>>> pLog-svn mailing list
>>> pLog-svn at devel.lifetype.net
>>> http://limedaley.com/mailman/listinfo/plog-svn
>>>
>>
>> _______________________________________________
>> pLog-svn mailing list
>> pLog-svn at devel.lifetype.net
>> http://limedaley.com/mailman/listinfo/plog-svn
>>
>
> _______________________________________________
> pLog-svn mailing list
> pLog-svn at devel.lifetype.net
> http://limedaley.com/mailman/listinfo/plog-svn
>

-- 
Jon Daley
http://jon.limedaley.com/

If it jams, force it.  If it breaks, it needed replacing anyway.
-- Lowery's Law