Finally I’ve made a complete switch to the DO4.X version and while using a DO4.3 RC3 have a few question about:
http://forum.x-tensive.com/viewtopic.php?f=29&t=5851&p=14371&hilit=FullText#p14371 If I understand this correctly “English” is a language name, right? If so how can it be used in combination with the Localization example? I know you decided not to implement the Localization as it’s done in 3.X branch because it could be easily substituted by a custom implementation and kindly provided an example of it. But right now I need to perform a fulltext searches on such columns. The question in this case would be how?
Thanks This thread was imported from our support forum. The original discussion may contain more detailed answer. Original topic by samirski. |
Alex (Xtensive) wrote:
Tony wrote:If "English" is full-text catalogue name on SQL Server" does this mean it only works with SQL Server, I was under the impression from early announcements that it works with postgres as well. Also originally I thought the plan was for you to implement your own text indexing, this sounds like it is the same as it was for DO3 originally before you implemented the Lucerne driver. The text indexing on DO3 was so limited, I started to implement my own Lucerne interface, luckily you came up with your own before I had done much work. I very much agree with the sentiments expressed in http://forum.x-tensive.com/viewtopic.php?f=56&t=5951&p=14853#p14853, future features seem to come and go and change with out updates on status, features are released without (and not even followed up later) documentation, it is getting very fustrating. Some examples of this: - I had to search to find any details of the text search, finally found it in a forum message. - Access control, long promised, but no updates on status.
A good start would be an a Roadmap that is kept uptodate. Also ether update the wiki or remove it. Alex (Xtensive) wrote:As far as I remember, "English" refers to full-text configuration name there. Concerning everything else - I agree, that's not really good at all, and I appologize for this. I'll publish reply there + will dedicate a special post to our roadmap on this week. Issue with upgrade tool @ 64 bit Windows is fixed. samirski wrote: Thank you Concerning full-text @ PostgreSQL: full-text configuration is described here: http://www.postgresql.org/docs/8.3/stat ... intro.html |