similar to: case sensitivity for untokenized fields

Hi .. I tried to exclude certain objects from my search, by adding appropriate term queries .. i = Ferret::Index::Index.new i.field_infos.add_field(:type, :index => :untokenized, :term_vector => :no) i << {:type => "Movie", :name => "Indiana" } i << {:type => "Movie", :name => "Forrest" } i << {:type =>

Hi, I have a user model that has a city field which is searchable using acts_as_ferret. But I can''t get it to return any result whether I use :city => {:store => :no, :index => :untokenized}, or :city => {:store => :no} in my User model''s acts_as_ferret option >>> User.find_by_contents("city:(cal poly)") =>

Hi, >> I never saw any mail system in which the local Part ist Case sensitive! > > Every Unix/Linux system (I?d say that represents the majority of mail systems) has a case sensitive local part. Most mail admins have set their systems up to normalize all users on lowercase names, but that is not and has not always been the case. at least in every large installation LDAP User

Hello ferret users, I have a problem with ferret dropping stored fields in the index. Not all fields I want to store get stored, so they can be searched, but can''t be retrieved in a search. Index creation: INDEX = Index::Index.new(:path => ''/home/gregor/wisa/index'', :analyzer => Analysis::WhiteSpaceAnalyzer.new) SR =

I''m getting "uninitialized constant UNTOKENIZED" when I try to do something like the following: class Url < ActiveRecord::Base acts_as_ferret :fields => {''name'' => {}, ''description'' => {}, ''url'' => {:index => Ferret::Document::Field::Index::UNTOKENIZED},

Gents, does this definition will allow me to search inside title, sub_title and url and sort by score, rank_sort, last_updated_at_sort ? acts_as_ferret :fields => { :title => {:boost => 2, :store => :yes}, :sub_title => {:store => :yes}, :url => {:store => :yes}, :rank_sort =>

I''m having problems sorting on untokenized fields. I have one field that sorts fine, but there are others that seem to sort on a different field. Here''s the index description: acts_as_ferret :remote=>true,:fields=>{:name=>{:boost=>2},:name_for_sort=>{:index => :untokenized}, :city=>{:boost=>2}, :city_for_sort=>{:index=>:untokenized},

Hi, I am working with an existing database that has table and field names such as ''TblUsers'' and ''txtEmailAddress''. Is rails sensitive to the case of the letters here? or can I simply refer to these tables and fields as ''tblusers'' and ''txtemailaddress'' in my controllers ad rhtml files? Also, the database has id fields

>> From: "Mark Hazen" <mhazen@franklin.uga.edu> >> Subject: Re: Network Neighborhood comment fields and Samba >> >>Have you tried commenting that string out in your smb.conf file, and letting >>the string be set first in the individual configs? That'd be my first >>suggestion. I have tried that, and that just forced the default comment of:

On 5 September 2017 at 17:27, FHDATA <fhdata at unm.edu> wrote: > > > hello, > > some users' login fails since they type upper > case for their user ids ,etc ... > > how can case sensitivity be disabled so they can login > with mix of upper and lower case? > > this is what i tried: > > in /etc/sssd/sssd.conf i tested this below > >

I'm trying to replace a robocopy solution with rsync due to the delta-byte transfers. Its working great (cwRsync), except.... I've been searching the list regarding case-sensitivity, and came across one thread, talking about HFS+ and copying two files that had the same name (X and x). Well I have a similar problem between 2 windows hosts, except *both* of them support case, but are

RoR-3.0.1 I have this case statement: case n.hll_normalize when "common name" @my_correspondent.correspondent_common_name = s when "legal name" . . . else raise ArgumentError, "#{n} attribute is not provided for." end hll_normalize is defined as: def hll_normalise strip.squeeze(" ").mb_chars.downcase end I

On 9/6/2017 3:45 AM, ken wrote: > I think it would also be a disservice to users, for case-insensitive > userids is not what they'll find on web sites and web services > throughout the rest of the world, even on their own phones. I agree with you on other points, but beware of this one. I've discovered that game logins, notably Blizzard, are case-insensitive. It's quite

On Tue, Oct 8, 2019, at 7:58 AM, Julian Kippels via dovecot wrote: > Hi, > > I have recently updated from Dovecot 2.2 to 2.3. Since I have noticed > that vacation responses from sieve are not working the same anymore. > For example, my sieve script looks like this: > > vacation :days 1 :addresses ["Kippels at hhu.de","julian.kippels at hhu.de"] >

Hi, I have some questions about searching with Ferret. I have a user index with first_name, last_name and full_name (which is just first plus last with a space). Here are a couple of questions: 1) If I store the fields tokenized, it appears as though queries are case-insensitive. However, for untokenized, the query is case-sensitive. How can I make the untokenized searches case-insensitive?

Forgive me if this topic has already been discussed on the list. I googled but couldn''t find much. I''d like to search through text for US state abbreviations that are written in capitals. What is the best way to do this? I read somewhere that tokenized fields are stored in the index in lowercase, so I am concerned that I will lose precision. What is the best way to store a

On 09/05/2017 06:01 PM, Yves Bellefeuille wrote: > FHDATA wrote: > >> some users' login fails since they type upper >> case for their user ids ,etc ... > Wouldn't it be better to explain to the users that the userid is case > sensitive? You probably don't want a system where Fhdata, FHData and > FHDATA are all possible and are different users. >

I have also posted this on IRC. I have a linux host running stock RHEL 5.4 Samba 3.0.33-3.15. The host acts both as a Samba server and does a CIFS mount of that same share. The reason for doing this is so that programs running on the Linux host have the same case insensitive view as the Windows clients. I have nocase set in the relevant line in /etc/fstab I have case sensitive = No set in the

Am 07.09.2017 um 20:07 schrieb hw: > Gordon Messmer wrote: >> On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: >>> This was always >>> problematic because DNS hostnames and email addresses in the RFC >>> standards were case insensitive >> >> >> Not quite.? SMTP is required to treat the "local-part" of the RCPT >> argument as

On 09/07/2017 08:11 AM, Stephen John Smoogen wrote: > This was always > problematic because DNS hostnames and email addresses in the RFC > standards were case insensitive Not quite.? SMTP is required to treat the "local-part" of the RCPT argument as case-sensitive, and to preserve case when relaying mail.? The destination is allowed to treat addresses according to local