On Thu, Dec 12, 2013 at 12:47 PM, Dev Kumkar devdas.kum...@gmail.comwrote:
+ hackers
On Thu, Dec 12, 2013 at 12:34 PM, Dev Kumkar devdas.kum...@gmail.comwrote:
On Wed, Dec 11, 2013 at 9:47 PM, Dev Kumkar devdas.kum...@gmail.comwrote:
Actually for searches lower will work.
But the other
Thanks John.
Yes CITEXT would work, the only thing its needs DDL changes across and
hence was looking for any such global database parameter setting while
creating database. I have been looking at other discussions and doesn't
look like anything of that coming up soon that makes database case
Can case-insensitive collation help here?
On Wed, Dec 11, 2013 at 4:55 PM, Dev Kumkar devdas.kum...@gmail.com wrote:
Thanks John.
Yes CITEXT would work, the only thing its needs DDL changes across and
hence was looking for any such global database parameter setting while
creating database.
On Wed, Dec 11, 2013 at 04:55:07PM +0530, Dev Kumkar wrote:
creating database. I have been looking at other discussions and doesn't
look like anything of that coming up soon that makes database case
insensitive.
You could build lower() indexes on any column you want to search CI
and lower()
Actually for searches lower will work.
But the other important aspect is 'inserts' which would result 2 rows if
the values are 'A' and 'a'. Intent here to have it case insensitive.
If CITEXT it will update the same row and works.
CITEXT is an alternative but was wondering if there is any other
On Wed, Dec 11, 2013 at 9:47 PM, Dev Kumkar devdas.kum...@gmail.com wrote:
Actually for searches lower will work.
But the other important aspect is 'inserts' which would result 2 rows if
the values are 'A' and 'a'. Intent here to have it case insensitive.
If CITEXT it will update the same
+ hackers
On Thu, Dec 12, 2013 at 12:34 PM, Dev Kumkar devdas.kum...@gmail.comwrote:
On Wed, Dec 11, 2013 at 9:47 PM, Dev Kumkar devdas.kum...@gmail.comwrote:
Actually for searches lower will work.
But the other important aspect is 'inserts' which would result 2 rows if
the values are 'A'
How to create case insensitive database?
I know about CITEXT data type, but what am looking for is if there any
parameter at database level which just makes the database case insensitive.
I mean both values 'ABC' and 'abc' are treated same for inserts and also
all the comparisons by default are
On 12/10/2013 10:31 PM, Dev Kumkar wrote:
I know about CITEXT data type, but what am looking for is if there any
parameter at database level which just makes the database case
insensitive.
there's nothing that will do that in postgres.
whats wrong with using CITEXT ?
--
john r pierce
Hi
I posted a similar question before. I was told that Postgres is always case
sensitive.
I was actually referring to text data not identifiers.
I mean char and varchar fields.
I basicically want to avoid using upper in comparisons.
With some databases you can use a utf8 characterset and a
On Mon, Jun 6, 2011 at 2:24 PM, Heine Ferreira heine.ferre...@gmail.com wrote:
Hi
I posted a similar question before. I was told that Postgres is always case
sensitive.
I was actually referring to text data not identifiers.
I mean char and varchar fields.
I basicically want to avoid using
On Mon, Jun 06, 2011 at 10:24:45PM +0200, Heine Ferreira wrote:
I basicically want to avoid using upper in comparisons.
Has anyone tried this?
Do you know if this will work?
There's a contrib module that will allow you to do this. See the
citext datatype.
A
--
Andrew Sullivan
Hi,
I'm moving over from MS SQL. I've been googling this for ages now and
suprisingly cannot find a clear answer.
I want my data in tables to be case insensitive.
This is so i can:
1. Put keys on natural key fields, for instance a product part number. I
product number 'ABC123' inserted i
Hello
you should to use a citext datatype
http://www.postgresql.org/docs/9.0/interactive/citext.html
regards
Pavel Stehule
2011/1/13 Phillip Smith phil...@softworks.com:
Hi,
I'm moving over from MS SQL. I've been googling this for ages now and
suprisingly cannot find a clear answer.
I
you should to use a citext datatype
http://www.postgresql.org/docs/9.0/interactive/citext.html
Or:
- use a functional index with lower() to ensure uniqueness
- use a BEFORE trigger to lower() the inserted data
Karsten
--
GMX DSL Doppel-Flat ab 19,99 Euro/mtl.! Jetzt mit
gratis
Thanks Pavel,
Is this the only way?. I would prefer to use a collation setting if this is
possible. Do you know whether there would be a performance hit using non
standard character strings?
Phillip
Hi Karsten,
modifying user inputted data is not an option for me. I need to maintain the
original data. I had read about indexing on a lower function. This all seems a
bit of a bodgy workaround to me. A clean Case Insensitive collation setting is
cleaner. Is this supported in postgreSQL 9?
2011/1/13 Phillip Smith phil...@softworks.com:
Thanks Pavel,
Is this the only way?. I would prefer to use a collation setting if this is
possible. Do you know whether there would be a performance hit using non
standard character strings?
It is preferred way. PostgreSQL doesn't support a
On Thu, Jan 13, 2011 at 03:29:03PM -, Phillip Smith wrote:
modifying user inputted data is not an option for me. I need to
maintain the original data. I had read about indexing on a lower
function. This all seems a bit of a bodgy workaround to me. A clean
Case Insensitive collation
Hi.
I have a little problem with user names and Postgres commands.
Due to quirks in corporate account management using ADS, some user names
come out as, say, Mickey when you log into Linux instead of mickey.
This unfortunate user tries to run Postgres commands and gets for
instance:
$
Will Rutherdale (rutherw) wrote:
When I try going into psql as user postgres to change the user name, I
get this problem:
postgres=# alter user mickey rename to Mickey;
ERROR: role “mickey” already exists
you might try...
alter user mickey rename to Mickey;
--
Sent via pgsql-general
...@cisco.com
Cc: pgsql-general@postgresql.org
Enviadas: Terça-feira, 24 de Março de 2009 17:21:20
Assunto: Re: [GENERAL] Case sensitivity problems with user name
Will Rutherdale (rutherw) wrote:
When I try going into psql as user postgres to change the user name, I get
this problem:
postgres
-general@postgresql.org
Subject: Re: [GENERAL] Case sensitivity problems with user name
Will Rutherdale (rutherw) wrote:
When I try going into psql as user postgres to change the user name, I
get this problem:
postgres=# alter user mickey rename to Mickey;
ERROR: role mickey already exists
On 24/03/2009 20:38, Will Rutherdale (rutherw) wrote:
Pardon my newness to Postgres.
We've all been there at some point! - except of course for Tom Lane.
:-)
Ray.
--
Raymond O'Donnell, Director of Music, Galway Cathedral,
On 24/03/2009 20:25, Berdam wrote:
aer
?
--
Raymond O'Donnell, Director of Music, Galway
*De:* John R Pierce pie...@hogranch.com
*Para:* Will Rutherdale (rutherw) ruth...@cisco.com
*Cc:* pgsql-general@postgresql.org
*Enviadas:* Terça-feira, 24 de Março de 2009 17:21:20
*Assunto:* Re: [GENERAL] Case sensitivity problems with user name
Will Rutherdale (rutherw) wrote:
When I try
Dear
Sirs,
I have a little
problem:
- Contest: Server
side: Linux Fedora core 4 with PostgreSQL v. 8.0
Client side: both Linux Fedora core 4 with pgAdmin III v. 1.4 and/or Windows
2000 server vith pgAdmin III v. 1.4
- I Made a
table:
CREATE TABLE "Accoglienza"(
"IdAccoglienza" int4
On Tue, 27 Dec 2005, dfx wrote:
Dear Sirs,
I have a little problem:
- Contest: Server side: Linux Fedora core 4 with PostgreSQL v. 8.0
Client side: both Linux Fedora core 4 with pgAdmin III v.
1.4 and/or Windows 2000 server vith pgAdmin III v. 1.4
- I Made a table:
CREATE
On 12/27/05, dfx [EMAIL PROTECTED] wrote:
Dear Sirs,
I have a little problem:
- Contest: Server side: Linux Fedora core 4 with PostgreSQL v. 8.0
Client side: both Linux Fedora core 4 with pgAdmin III v.
1.4 and/or Windows 2000 server vith pgAdmin III v. 1.4
- I Made a
Due to case weirdness in Postgres, particularly when accessing it from
PHP, I completely abandoned mixed case table and column names. I don't
know if things have changed in the past several years, but when I first
made the leap, mixed case was more trouble than it was worth.
Even after I got
On Tue, Dec 27, 2005 at 09:14:20AM -0600, John McCawley wrote:
Due to case weirdness in Postgres, particularly when accessing it from
PHP, I completely abandoned mixed case table and column names. I don't
know if things have changed in the past several years, but when I first
made the
Well, the rule is very simple, either always quote your identifiers, or
never quote them. If you always quote them, then you always need to
specify them in the same case. If you never quote them, then you always
get case-insensetivity.
My memory is a little hazy, as it's been a few years,
Hi,
On Tue, 2005-12-27 at 15:54 -0800, dfx wrote:
How I can set case-insensitive the system, or avoid the conversion to
lower case?
You need to double-quote the object names that you don't want to be
converted to lower case, like CREATE TABLE DevrimGunduz.
Regards,
--
The PostgreSQL Company
Frank Millman wrote:
Hi all
Is there an LC_COLLATE setting, or any other method, which
allows all
data in a database to be treated in a case-insensitive manner?
Thanks for all the replies, guys, I really appreciate it.
Here is what I have decided to do. If anyone sees any problems with
Frank Millman wrote:
1. Will SELECT WHERE LOWER(colname) = 'a001' use the index, or must I
create a separate index on LOWER(colname)?
Sorry. RTFM. The docs clearly state that this is necessary.
Frank
---(end of broadcast)---
TIP 6: explain
To handle searching for a row based on a string, I will use
LOWER(colname)
= 'x' and LOWER(colname) LIKE 'x%'. AFAICT, the second one is
equivalent
to colname ILIKE 'x%', provided I force 'x' to lowercase first.
I would strongly suggest you do this instead:
LOWER(colname) = LOWER('x')
# [EMAIL PROTECTED] / 2005-08-10 13:18:32 +0200:
1. Will SELECT WHERE LOWER(colname) = 'a001' use the index, or must I create
a separate index on LOWER(colname)?
the latter
--
How many Vietnam vets does it take to screw in a light bulb?
You don't know, man. You don't KNOW.
Cause you
Frank Millman wrote:
Hi all
Is there an LC_COLLATE setting, or any other method, which allows all
data in a database to be treated in a case-insensitive manner?
I was hoping to stimulate some discussion on this topic, but it seems I will
have to kick-start it myself and see if anyone
On Tue, Aug 09, 2005 at 09:35:25AM +0200, Frank Millman wrote:
Frank Millman wrote:
Hi all
Is there an LC_COLLATE setting, or any other method, which allows all
data in a database to be treated in a case-insensitive manner?
I was hoping to stimulate some discussion on this topic,
On Tue, Aug 09, 2005 at 11:57:48AM +0200, Martijn van Oosterhout wrote:
Another option would be to create a new datatype 'itext' which works
like text except it compares case insensetively. PostgreSQL is flexible
like that. Here's something to get you started, see below for example.
Frank Millman wrote:
Frank Millman wrote:
Hi all
Is there an LC_COLLATE setting, or any other method, which allows all
data in a database to be treated in a case-insensitive manner?
I was hoping to stimulate some discussion on this topic, but it seems I will
have to kick-start it myself
Martijn van Oosterhout kleptog@svana.org writes:
Another option would be to create a new datatype 'itext' which works
like text except it compares case insensetively. PostgreSQL is flexible
like that. Here's something to get you started, see below for example.
On Tue, Aug 09, 2005 at 11:02:47AM -0400, Tom Lane wrote:
Martijn van Oosterhout kleptog@svana.org writes:
Another option would be to create a new datatype 'itext' which works
like text except it compares case insensetively. PostgreSQL is flexible
like that. Here's something to get you
Frank Millman wrote:
Hi all
Is there an LC_COLLATE setting, or any other method, which allows all data
in a database to be treated in a case-insensitive manner?
I have two scenarios in mind. There are workarounds for both of them, but it
would be nice if they were not necessary.
1. In a
Hi all
Is there an LC_COLLATE setting, or any other method, which allows all data
in a database to be treated in a case-insensitive manner?
I have two scenarios in mind. There are workarounds for both of them, but it
would be nice if they were not necessary.
1. In a UNIQUE column, I would like
I looked into the problem further - and could not repeat the problem on
my windows XP machine. The problem was isolated to a server which uses
the 64bit edition of W2K3 server. Otherwise the W2K3 64bit edition seems
to run PG ok.
Are there any plans for fixing the UNICODE encoding on Windows?
I looked into the problem further - and could not repeat the
problem on my windows XP machine. The problem was isolated to
a server which uses the 64bit edition of W2K3 server.
Otherwise the W2K3 64bit edition seems to run PG ok.
Are there any plans for fixing the UNICODE encoding on
Tom, Magnus.
Thanks for the great support.
Howard Cole
www.selestial.com
Magnus Hagander wrote:
Are there any plans for fixing the UNICODE encoding on Windows?
Yes. There is a patch floating around to use ICU, which will fix this
(amongst the other things it does). The hope is that
Has case sensitivity changed between 8.0.1 and 8.0.3 or am I missing
some setting somewhere?
I try the following sql on two database servers and get different results:
create table test (val varchar(10));
insert into test values ('A');
insert into test values ('a');
select * from test where
create table test (val varchar(10));
insert into test values ('A');
insert into test values ('a');
select * from test where val 'a';
Results on 8.0.1 linux server (UNICODE)
val
-
(0 rows)
Results on 8.0.3 windows server (UNICODE) val
-
A
(1 row)
I am guessing that
Howard Cole [EMAIL PROTECTED] writes:
Has case sensitivity changed between 8.0.1 and 8.0.3
Nope.
Results on 8.0.3 windows server (UNICODE)
Unicode doesn't work at all well on Windows. Consider using a different
encoding. Also, you'd better check that you have matching locale and
encoding
Jason Tesser wrote:
I am converting data from Access into Postgres and ran into an issue
with case sensitivity. Can I write queries in Access that will be case
insensitive without rewriting the queries. So I would like to know if
this be handled in Postgres or even if someone knows in Access.
I am converting data from Access into Postgres and ran into
an issue with case sensitivity. Can I write queries in Access that will be case
insensitive without rewriting the queries.
So I would like to know if this be handled in Postgres or even if
someone knows in Access. Thank you.
On Sunday 11 January 2004 09:29, Dario Ottaviano wrote:
I use postgres on a window server (IIS 5.1)
Is there anybody that knows if is possible to make postgres no case
sensitive in the manipulating data into tables/views?
There's no general case_sensitive = yes/no flag. There are
On Mon, 12 Jan 2004, Richard Huxton wrote:
On Sunday 11 January 2004 09:29, Dario Ottaviano wrote:
I use postgres on a window server (IIS 5.1)
Is there anybody that knows if is possible to make postgres no case
sensitive in the manipulating data into tables/views?
There's no general
select * from Apples where lower(color) like '%red%';
ech`echo xiun|tr nu oc|sed 'sx\([sx]\)\([xoi]\)xo un\2\1 is xg'`ol
Känns det oklart? Fråga på!
On 9 Sep 2001, Michael Gay wrote:
If I am doing a command such as
select * from Apples where color like '%red%';
how do I make it case
Szabo Zoltan [EMAIL PROTECTED] writes:
Use: ILIKE
If I am doing a command such as
select * from Apples where color like '%red%';
how do I make it case insensitive?
I was trying to solve a similar problem where I wanted an exact match to work
in PostgreSQL and MySQL and ended up with:
If I am doing a command such as
select * from Apples where color like '%red%';
how do I make it case insensitive?
Thanks.
mike
---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
12:02 AM
Subject: [GENERAL] Case sensitivity issue
If I am doing a command such as
select * from Apples where color like '%red%';
how do I make it case insensitive?
Thanks.
mike
---(end of broadcast)---
TIP 1: subscribe and unsubscribe
use ILIKE instead of LIKE
or use a regular expression match: ~* 'red'
- Original Message -
From: Michael Gay [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Sunday, September 09, 2001 11:02 PM
Subject: [GENERAL] Case sensitivity issue
If I am doing a command such as
select * from
Very good book. I have the .pdf file of it from before they took it off
the site.
John Clark Naldoza y Lopez wrote:
Hello Scott,
PostgreSQL also supports regular expressions, _VERY_ useful..;-)
~* regular expression, case-insensitive..;-)
Try to get a copy of Bruce's book
Hello Scott,
PostgreSQL also supports regular expressions, _VERY_ useful..;-)
~* regular expression, case-insensitive..;-)
Try to get a copy of Bruce's book
Introduction and Concepts
by Bruce Momjian
A sample from the book:
SELECT * FROM friend WHERE firstname ~* '[bc]'
read it online,
We intend to move from M$ Access to PostgreSQL, however, much of our legacy
code operates under the assumption that string or text comparisons are case
insensitive whereas postgres is case sensitive. This issue extends to SQL
Select statements as well as straight comparison (i.e. in addition to
Bruce Richardson wrote:
Discovering that text fields in Postgres are case sensitive - so "Text"
"text" and both can go into the same UNIQUE column - threw me a bit,
as this is different from other databases I've worked with.
Well, they are different, aren't they?
Is there a toggle to
64 matches
Mail list logo
