Closed (fixed)
Project:
Taxonomy Query Language
Version:
5.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Mar 2007 at 10:18 UTC
Updated:
26 Mar 2007 at 23:46 UTC
Could you surport Chinese query
Comments
Comment #1
rötzi commentedI tried now adding the "\w" word character class to the regular expression match. This should match all characters which your setup see's as a part of a word, so if the setup is chinese I hope it will match chinese characters. It's in CVS, so either get it from there or wait until the new dev package is created.
What is alredy working is using quotes, so using
"⾿⾵"as a search term should alredy work, but this does not work with autocompletion.So I would be glad if you can try the new dev version when it is ready. And if it does not work without the quotes there, we have to find a better regular expression for this. At the moment it is
/[\w_a-zA-Z0-9]+/, where I hope that the\wwill match chinese characters in your setup. If it does not I would be glad for some help how to make a regular expression which does match chinese (and other) characters.Comment #2
rötzi commentedI updated the module again. Now it should work with chinese characters, also autocompletion.
I would be glad if you could do some tests - with quotes, without quotes and autocompletion - and tell me if it works.
Comment #3
yipee commentedrötzi
Thank you for your great job.
It work very well as plugin for search (Drupal core). But useing it as Views filter, I got following erro:
Could you check and fix it?
Thanks
Comment #4
rötzi commentedCan you tell me which MySQL version you are using?
I tested MySQL '4.1.20' and '5.0.24', maybe it's a version problem.
And which other filters you activated in your view, then I can check if it is a compatibility problem with other fitlers.
Comment #5
rötzi commentedAt a second glance it looks like a problem of Views. The query you show has a part " DISTINCT(node.nid) in" which is wrong. But the tql module only creates the text "node.nid in" which would be correct. Thus it is probably a Views problem, not a MySQL one. It could be that Views or another filter adds the 'DISTINCT' around the 'node.nid'.
Which version of Views have you installed?
Comment #6
rötzi commentedIt probably is the 'node: Distinct' fitler. Can you remove that one and test if it works?
Comment #7
yipee commentedYes you are right. when I removed the Distinct' fitler, It works.
I hope you can find solution.
Comment #8
rötzi commentedThis is the solution ;)
I don't think there occur any duplicates with the tql filter, so the 'node: Distinct' filter should not be needed at all. But if you see any duplicates please report.
I set this to fixed. If you have problems with duplicates, please reopen or make a new issue.
Comment #9
(not verified) commented