Very interesting discussion indeed.
It seems that "Postgresql:The world's most advanced open source database" can
not work properly on "Mac OS X: the world's most advanced operating system" and
FreeBSD.
Don't you think postgresql.org should remove from their download page the links
to FreeBSD
On Sat, Jan 16, 2010 at 09:10:53PM +, Greg Stark wrote:
> Switching to ICU means trading our current inconsistency from platform
> to platform for a different inconsistency which would be better in
> some cases and worse in others.
Or, you can have the cake and eat it too. That is, aim for the
On Thu, Jan 14, 2010 at 6:15 AM, Craig Ringer
wrote:
>>> Out of interest: Why not?
>>
>> There's plenty of discussion in the archives about it, but basically
>> ICU would represent a pretty enormous dependency and would lock us in
>> to having no other backend encoding but UTF8.
>
> Thanks. You're
Scott Marlowe wrote:
> On Wed, Jan 13, 2010 at 11:15 PM, Craig Ringer
> wrote:
>> Perhaps someone who wants to use Mac OS X and Pg for their product will
>> come forward with some compat wrapper functions for the localizable
>> libc/posix functions, so Pg can just be built against the wrapper and
Craig Ringer writes:
> Tom Lane wrote:
>> The state of OS X's POSIX-spec locale support is pretty pitiful, but on
>> the whole I'd say if you need better UTF8 locale support you could use
>> another OS.
> Alas, people will want to run Pg on it anyway, especially when bundling
> with an app. It'd
On Wed, Jan 13, 2010 at 11:15 PM, Craig Ringer
wrote:
> Perhaps someone who wants to use Mac OS X and Pg for their product will
> come forward with some compat wrapper functions for the localizable
> libc/posix functions, so Pg can just be built against the wrapper and
> the rest of us need not ca
Tom Lane wrote:
> Craig Ringer writes:
>> Martijn van Oosterhout wrote:
>>> Yes, that's the basic idea. Mac OS X apparently provides ICU underneath
>>> for programs that would like true unicode collation, but there is
>>> little chance that postgresql will ever use this.
>
>> Out of interest: Why
Craig Ringer writes:
> Martijn van Oosterhout wrote:
>> Yes, that's the basic idea. Mac OS X apparently provides ICU underneath
>> for programs that would like true unicode collation, but there is
>> little chance that postgresql will ever use this.
> Out of interest: Why not?
There's plenty of
Martijn van Oosterhout wrote:
>> in a UTF8 text file and use the "sort" command on it, you will have the same
>> wrong output as with PostgreSQL :
>
> Yes, that's the basic idea. Mac OS X apparently provides ICU underneath
> for programs that would like true unicode collation, but there is
> lit
On 13/01/2010 11:15 PM, Martin Flahault wrote:
It seems there is a problem with the collating order on BSD systems with
diacritics using UTF8.
If you put this text :
a
A
à
é
e
E
in a UTF8 text file and use the "sort" command on it, you will have the
same wrong output as with PostgreSQL :
A
E
a
On Wed, Jan 13, 2010 at 04:15:06PM +0100, Martin Flahault wrote:
[postgres]
> newbase=# select * from t1 order by contenu;
> contenu
> -
> A
> E
> a
> e
Postgresql outputs whatever the C library does on the underlying
system. The quality of this varies wildly.
> à
> As with others
Here is an exemple :
postgres=# create database newbase;
CREATE DATABASE
postgres=# \c newbase;
psql (8.4.2)
You are now connected to database "newbase".
newbase=# create table t1 (contenu text);
CREATE TABLE
newbase=# insert into t1 values ('a'), ('e'), ('à'), ('é'), ('A'), ('E');
INSERT 0 6
ne
On 12/01/2010 7:36 PM, Martin Flahault wrote:
Hi,
We are a software publisher searching for a new DBMS for our software.
We have more than one hundred installed servers, running Mac OS and a
Primebase database.
We have spend some time evaluating PostgreSQL and we can't get correct
outputs with
Am 12.01.2010 um 12:36 schrieb Martin Flahault:
> We have spend some time evaluating PostgreSQL and we can't get correct
> outputs with the ORDER BY command.
> LC_COLLATE and LC_CTYPE are set to fr_FR.UTF-8.
>
> It seems there is a known problem with the collating order of text including
> diac
Hi,
We are a software publisher searching for a new DBMS for our software. We have
more than one hundred installed servers, running Mac OS and a Primebase
database.
We have spend some time evaluating PostgreSQL and we can't get correct outputs
with the ORDER BY command.
LC_COLLATE and LC_CTYPE
David Harel napsal(a):
Hi,
I'm new here. I work on a site that uses postgres version 8.1.5 and
database encoding ISO_8859_8. When I sort select requests using order by
the "weight" of the characters seem to be really funny (but consistent).
It seems to me that if I create a "phantom" converte
Hi,
I'm new here. I work on a site that uses postgres version 8.1.5 and
database encoding ISO_8859_8. When I sort select requests using order by
the "weight" of the characters seem to be really funny (but consistent).
It seems to me that if I create a "phantom" converted field such as:
SELECT
Tom Lane wrote:
Kevin Murphy <[EMAIL PROTECTED]> writes:
What is the answer to Filip's question? I didn't see an answer in the list
archives. I've seen several copies of Joe Conway's pg_strxfrm.c code on the
web, and it always refers to the Warn_restart variable, which doesn't seem to
exist
Kevin Murphy <[EMAIL PROTECTED]> writes:
> What is the answer to Filip's question? I didn't see an answer in the list
> archives. I've seen several copies of Joe Conway's pg_strxfrm.c code on the
> web, and it always refers to the Warn_restart variable, which doesn't seem to
> exist in the 8.1
Filip Rembiałkowski wrote:
Greg Stark wrote:
But the closest partial solution suggested so far is the pg_xfrm (sic)
function that
has been implemented and posted at least three times by three different
posters to the postgres mailing lists. In the interest of avoiding a fourth
i
Filip Rembiałkowski wrote:
let's assume that we keep Unicode text data in the column.
sometimes we want to sort it according to specific collation order.
how can we force collation when running a query?
Hi Filip,
I had the same problem you have. As a solution I implemented a wrapper
function
Martijn van Oosterhout writes:
> On Wed, Jun 07, 2006 at 12:40:49AM +0400, Nikolay Samokhvalov wrote:
>> What is 'lack of interest'? Interest from community, or major
>> developers, or your personal one?
> Kind of all three, feeding off eachother. There's just not enough
> interest from any front
On 6/7/06, Martijn van Oosterhout wrote:
Kind of all three, feeding off eachother. There's just not enough
interest from any front to really get it moving. It's a fairly invasive
change and without significant support and interest from somewhere,
chances of completion let alone acceptance are p
On Wed, Jun 07, 2006 at 12:40:49AM +0400, Nikolay Samokhvalov wrote:
> I were looking forward to this feature... So many troubles in my
> projects would be vanished...
>
> What is 'lack of interest'? Interest from community, or major
> developers, or your personal one?
Kind of all three, feeding
(group dupe)
05 Jun 2006 12:53:57 -0400, Greg Stark <[EMAIL PROTECTED]>:
But the closest partial solution suggested so far is the pg_xfrm function that
has been implemented and posted at least three times by three different
posters to the postgres mailing lists. In the interest of avoiding a fo
On 6/5/06, Martijn van Oosterhout wrote:
Yeah, I was working on it but got stuck on the planner/optimiser
changes. In the mean time the tree drifted and lack of interest, which
gets us where we are now...
Very bad news :-(
I were looking forward to this feature... So many troubles in my
proje
"Filip Rembiaâkowski" <[EMAIL PROTECTED]> writes:
> let's assume that we keep Unicode text data in the column.
> sometimes we want to sort it according to specific collation order.
> how can we force collation when running a query?
> ideal solution would be having SQL92 standard COLLATE clauses i
On Mon, Jun 05, 2006 at 05:04:25PM +0200, Filip Rembia??kowski wrote:
> Hi all,
>
> let's assume that we keep Unicode text data in the column.
> sometimes we want to sort it according to specific collation order.
> how can we force collation when running a query?
> ideal solution would be having
Hi all,
let's assume that we keep Unicode text data in the column.
sometimes we want to sort it according to specific collation order.
how can we force collation when running a query?
ideal solution would be having SQL92 standard COLLATE clauses in
SELECT statements. I heard it's work in progres
talenat wrote:
talenat wrote:
Hi,
I have a mandrake 10.1 server running Postgres 8.1beta3 with hr_HR
locale. Client is a XP with WIN1250 code page.
When I use ORDER BY in query collation is out of order.
I have tried with client encoding WIN1250 and LATIN2 but with no luck.
If I use XP as a s
talenat wrote:
Hi,
I have a mandrake 10.1 server running Postgres 8.1beta3 with hr_HR
locale. Client is a XP with WIN1250 code page.
When I use ORDER BY in query collation is out of order.
I have tried with client encoding WIN1250 and LATIN2 but with no luck.
If I use XP as a server with postgr
Hi,
I have a mandrake 10.1 server running Postgres 8.1beta3 with hr_HR
locale. Client is a XP with WIN1250 code page.
When I use ORDER BY in query collation is out of order.
I have tried with client encoding WIN1250 and LATIN2 but with no luck.
If I use XP as a server with postgres 8.1beta3 then
32 matches
Mail list logo
