Tom Lane wrote:
Dragan Matic [EMAIL PROTECTED] writes:
I was about to say the same thing. I think that the whole point in
having a portable database system is that the data inside the database
should behave the _same way_ no matter what operating system database is
running on - client
On Mon, Jul 03, 2006 at 12:55:18AM -0400, Tom Lane wrote:
Fine for you, not so fine for other people with different concerns.
I'm not unsympathetic to your general point, but black-and-white
arguments won't get far in this discussion. It's all about tradeoffs
... it's most definitely not
On Sat, Jul 01, 2006 at 06:23:07PM -0400, Tom Lane wrote:
Tomi NA [EMAIL PROTECTED] writes:
Basically, it comes down to three possibilities, doesn't it:
1.) use an existing library
2.) write a pgsql specific implementation
3.) forget about it and tend to other issues
Personally, I
Tomi NA wrote:
On 6/30/06, Martijn van Oosterhout kleptog@svana.org wrote:
On Fri, Jun 30, 2006 at 11:56:19AM +0200, Dragan Matic wrote:
I have two postgres servers, one on linux (fedora core 5), one on
windows, both are version 8.1.4.
Not beeing able to depend on the engine to
On Sun, Jul 02, 2006 at 12:13:02PM +0200, Martijn van Oosterhout wrote:
However, the most important point is that people have said they'll take
the speed hit if they could get consistant collation.
I can second that.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD
On Jul 2, 2006, at 6:13 AM, Martijn van Oosterhout wrote:
But I don't think anyone is actually considering importing ICU into the
postgres source tree, are they?
Why not?
Size - I'm not sure this is relevent since I don't think we want to
incorporate it into postgres itself, just let people
On 7/2/06, Agent M [EMAIL PROTECTED] wrote:
Certain Japanese characters cannot make a reliable round-trip through
Unicode. ICU uses UTF-16 as its store, so the Japanese folks won't be
happy with an ICU-only solution. However, it would still be of great
Could you explain what you mean and
On Sun, Jul 02, 2006 at 12:25:43PM -0400, Agent M wrote:
On Jul 2, 2006, at 6:13 AM, Martijn van Oosterhout wrote:
But I don't think anyone is actually considering importing ICU into the
postgres source tree, are they?
Why not?
Because it's a project of similar size to postgres and probably
Dragan Matic [EMAIL PROTECTED] writes:
I was about to say the same thing. I think that the whole point in
having a portable database system is that the data inside the database
should behave the _same way_ no matter what operating system database is
running on - client shouldn't be aware of
On Fri, Jun 30, 2006 at 07:29:12PM +0200, Tomi NA wrote:
If I sound harsh, please excuse me, but I feel like I'm the only one
who thinks these encoding problems (collation, upper/lowercase,
multiple languages in a single database) are serious...nobody seems to
share the sentiment. Ah well...
On 7/1/06, Martijn van Oosterhout kleptog@svana.org wrote:
On Fri, Jun 30, 2006 at 07:29:12PM +0200, Tomi NA wrote:
If I sound harsh, please excuse me, but I feel like I'm the only one
who thinks these encoding problems (collation, upper/lowercase,
multiple languages in a single database) are
Tomi NA [EMAIL PROTECTED] writes:
Basically, it comes down to three possibilities, doesn't it:
1.) use an existing library
2.) write a pgsql specific implementation
3.) forget about it and tend to other issues
Personally, I don't really care if it's 1) or 2): I'm just afraid it's
going to
I have two postgres servers, one on linux (fedora core 5), one on
windows, both are version 8.1.4.
Both databases are initialized with locale Croatian and win1250 encoding.
running pg_controldata on windows returns this
LC_COLLATE: Croatian_Croatia.1250
LC_CTYPE:
On Fri, Jun 30, 2006 at 11:56:19AM +0200, Dragan Matic wrote:
I have two postgres servers, one on linux (fedora core 5), one on
windows, both are version 8.1.4.
Both databases are initialized with locale Croatian and win1250 encoding.
running pg_controldata on windows returns this
14 matches
Mail list logo
