Displaying 20 results from an estimated 11000 matches similar to: "Default value for case sensitive on uniqueness validator"
2006 Apr 20
7
Rails + postgres case insensitive searches.
Hello all
I am wondering how rails handles case sensitivity in databases. If I
do a Person.find_all_by_name("tim") in mysql I would expect to get
tim, TIm, and Tim. Do I only get tim in postgres?
How do other people deal with this? Do you resort to find_by_sql for
all your postgres queries to get case insensitive results?
2006 Mar 10
5
case insensitive search
I am having trouble with a simple gallery search.
I type in a segment of the address and i only
seem to be getting results if I use the correct case.
This is in my Gallery controller:
def search
@gallery = Gallery.find(:all, :include => :property,
:conditions => "address LIKE ''%#{@params[:keywords]}%''")
end
On a different note:
I am having
2019 Sep 11
5
[Bug] Sieve vacation :addresses match only,> case-sensitive?
> I want to have it case-insensitive again, like in Pigeonhole version 0.4.24
i would also plea for making it case-insensitive again! We were hit by this too,
and I never saw any mail system in which the local Part ist Case sensitive!
Sincerly,
Klaus Steinberger
--
Rechnerbetriebsgruppe / IT, Fakult?t f?r Physik
Klaus Steinberger
FAX: +49 89 28914280
Tel: +49 89 28914287
--------------
2019 Sep 09
1
[Bug] Sieve vacation :addresses match only case-sensitive?
> On 9 Sep 2019, at 16.17, Philipp Faeustlin via dovecot <dovecot at dovecot.org> wrote:
>
>> It is not recommended to rely on local-part case, but it is indeed
>> case-sensitive.
>> And this is to avoid such issues that postfix supports address
>> cleanup/canonicalisation before forwarding mails to dovecot.
>> ----------
>> RFC
2006 Mar 29
3
MySQL in dev, Postgres in prod - differences in "LIKE" query
Hi everyone,
I run MySQL in my dev environment, but Postgres in my production
environment (out of necessity). I''m having trouble finding a way to
write a query with a LIKE condition that is supported as case
insensitive in both databases.
Right now, I have this:
@query = "m" # for example
@people = Person.find(:all, :conditions => ["last_name LIKE ?", @query +
2017 Mar 03
2
case sensitive hostname matching
Hi,
as recently noticed by one of our customers, ssh tends to perform
hostname matching in a case sensitive manner since the lowercasing has
been delayed till after configuration parsing (by commits
d56b44d2dfa093883a5c4e91be3f72d99946b170 and
eb6d870a0ea8661299bb2ea8f013d3ace04e2024).
Given that hostnames are ususally interpreted in a case insensitive way
(and the code actually expects the
2019 Sep 04
2
[Bug] Sieve vacation :addresses match only case-sensitive?
On Wed, Sep 4, 2019 at 8:25 AM Philipp Faeustlin via dovecot <
dovecot at dovecot.org>
> Further investigation showed me that it has to be a bug.
>
> I tested with Dovecot 2.2.36.3 (a7d78f5a2), Pigeonhole version 0.4.24
> (5a7e9e62):
>
> In this version the additional addresses in vacation :addresses
> ["test at example.com"] are handled case-insensitive.
>
2019 Sep 02
4
Sieve vacation :addresses match only case-sensitive?
The recipients in the vacation :addresses String list are matched
case-sensitive.
If the recipient gets a mail with wrong case, the message is discarded with:
"discarding vacation response for implicitly delivered message; no known
(envelope) recipient address found in message headers"
I think the matching should be case-insensitive.
Is this a bug or do I miss some option?
I'm
2024 Jun 07
2
4.20: case (in)sensitive is broken
Hi!
This is a heads-up for now, more debugging to follow.
I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20
broke case insensitive file access entirely. Only exact case
filename works, no matter which value is set in "case sensitive"
parameter.
In 4.19, things works again.
/mjt
--
GPG Key transition (from rsa2048 to rsa4096) since 2024-04-24.
New key:
2006 Apr 19
2
How to do case-sensitive searches
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
2017 Mar 01
7
[Bug 2685] New: Case sensitive hostname matching
https://bugzilla.mindrot.org/show_bug.cgi?id=2685
Bug ID: 2685
Summary: Case sensitive hostname matching
Product: Portable OpenSSH
Version: 7.4p1
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: P5
Component: ssh
Assignee: unassigned-bugs at mindrot.org
2019 Sep 04
2
[Bug] Sieve vacation :addresses match only case-sensitive?
>
> It is not recommended to rely on local-part case, but it is indeed
> case-sensitive.
>
> And this is to avoid such issues that postfix supports address
> cleanup/canonicalisation before forwarding mails to dovecot.
>
> ----------
> RFC 5321:
>
> "Local-part = Dot-string / Quoted-string ; MAY be case-sensitive
> [?]
> While the above definition
2013 May 07
3
validates :uniqueness apparently doesn't
ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.3.0]
Rails 3.2.13
I have a validates ... :uniqueness constraint on one of the attributes
of an ActiveRecord class.
In my test suite, I set the attribute from the same attribute in a
record in the fixture. I then send invalid? to the object under test.
invalid? returns _false_, and the .errors object for the record shows no
errors.
A
2020 Nov 09
1
DOP-1414 sieve vacation address matching is case sensitive
Hello,
One year ago a bug was reported regarding pigeonhole vacation plugin
https://www.mail-archive.com/dovecot at dovecot.org/msg78588.html
a mail sent to User at domain.com instead of user at domain.com will generate a "
vacation action: discarding vacation response for implicitly delivered
message; no known (envelope) recipient address found in message headers
(recipient=<user at
2024 Jun 07
1
4.20: case (in)sensitive is broken
On 6/7/24 9:34 AM, Michael Tokarev via samba wrote:
> I had to downgrade samba from 4.20.1 to 4.19.6 because 4.20
> broke case insensitive file access entirely.? Only exact case
> filename works, no matter which value is set in "case sensitive"
> parameter.
hm, can't reproduce:
$ bin/smbclient -U "slow%x" //localhost/test
smb: \> ls foo
foo N
2017 Sep 06
2
login case sensitivity
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.
>
2006 Oct 24
2
Question about Case Insensitivity
Hi,
I am trying to make a Linux filesystem appear case-insensitive and I got the
idea that I could use a SAMBA loopback mount to do this. I almost succeeded on
my first try but I ran into a snag I have no answer for yet.
My setup involves sharing filesystem "/a" and then mounting it on "/b". I can
use "ls -l" on the "/b" filesystem in a case-insensitive
2014 Mar 02
2
Using ZFS Case insensitive filesystems with Samba
>> Here's something I learned when working with the FreeNAS folks :
>> ZFS can be configured to be case insensitive when
>> you create the filesystem (NOTE - cannot be altered
>> *after* the filesystem is created).
>> zfs create -o casesensitivity=insensitive filesystem
In this case, will ZFS preserve capitals in file and directory names if they are so created
2006 Jan 09
3
Pagination :conditions not working - MySQL v. PostgreSQL, Rails abstraction v. embedded SQL
Hi everyone,
I have this code:
@person_pages, @people = paginate :person, :per_page => 20,
:conditions => [ "username LIKE ? OR first_name LIKE ? OR
last_name LIKE ? OR preferred_name LIKE ?",
"%" + params[:q].downcase + "%",
"%" + params[:q].downcase + "%",
2010 Feb 17
1
Unwanted case sensitivity
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