On Nov 4, 2006, at 11:34 , Martijn van Oosterhout wrote:
On Sat, Nov 04, 2006 at 04:23:02PM +0100, Alain Roger wrote:
however, when i do this, my encoding is in UTF-8 via phpAdmin.
UTF8 is a part of UNICODE, but as i'm not sure on how many bits is
UNICODE,
how can i setup my local DB to UNI
Yes, my provider has v8.0.1 and i have installed v8.1.4.thanks for your confirmation.Al.On 11/4/06, Martijn van Oosterhout <
kleptog@svana.org> wrote:On Sat, Nov 04, 2006 at 04:23:02PM +0100, Alain Roger wrote:
> however, when i do this, my encoding is in UTF-8 via phpAdmin.> UTF8 is a part of UNIC
On Sat, Nov 04, 2006 at 04:23:02PM +0100, Alain Roger wrote:
> however, when i do this, my encoding is in UTF-8 via phpAdmin.
> UTF8 is a part of UNICODE, but as i'm not sure on how many bits is UNICODE,
> how can i setup my local DB to UNICODE value as my provider has ?
As far a postgres is conce
I am not sure what locale I was running as I had not set it when doing initdb.
I created a new DB with --locale=en_US.utf8 -E UNICODE
and imported my data from original source (not copied from old DB) and still
have the smae problem that UNICODE strings with double byte characters that are
not e
"Grant Morgan" <[EMAIL PROTECTED]> writes:
> = is not working on a char(30) coloumn for me.
> I want to find rows with equal name.
> I have my database set to unicode.
I'll bet you are running the postmaster in a locale that isn't expecting
utf-8 encoding. The locale and encoding have to match or
-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peter Eisentraut
Sent: May 6, 2005 2:12 AM
To: Mark Borins
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Unicode and unaccent()
Mark Borins wrote:
> My problem is that the values like \342 are for LATIN1 type encodi
Mark Borins wrote:
> The encoding on my DB is Unicode, so far I have found an unaccent() function
> by looking in the mail archives it looks like the following:
>
>
> CREATE FUNCTION unaccent(text) RETURNS text AS $$
>BEGIN
>RETURN translate($1, '\342\347\350\351\352\364\373'
Mark Borins wrote:
> My problem is that the values like \342 are for LATIN1 type encoding.
> I have tried and failed to get this working using the what I think
> is the Unicode escaping method \u0032 for example.
There is no Unicode escaping method. You need to encode the characters
into UTF-8
On Fri, 10 Sep 2004 14:57:18 +0200, Michael Wimmer <[EMAIL PROTECTED]> wrote:
(...)
> Is there a way to make this work in 7.4.x too?
> May problem is that we are in a rush to do a port of our application
> from informix and I will not be able to wait until 8.0 will be released.
What encoding does
All of the ISO 8xxx encodings and LATINX encodings can handle two langauges, English and at least one other. Sometimes they can handle several langauges besides English, and are actually designed to handle a family of langauges.
The ONLY encodings that can handle a significant amount of multiple
> On Wed, 23 Jun 2004, Dennis Gearon wrote:
>
> > This is what has to be eventually done:(as sybase, and probably others do it)
> >
> > http://www.ianywhere.com/whitepapers/unicode.html
>
> Actually, what probably has to be eventually done is what's in the SQL
> spec.
>
> Which is AFAICS bas
On Wed, 23 Jun 2004, Dennis Gearon wrote:
> This is what has to be eventually done:(as sybase, and probably others do it)
>
> http://www.ianywhere.com/whitepapers/unicode.html
Actually, what probably has to be eventually done is what's in the SQL
spec.
Which is AFAICS basically:
Allow mu
12 matches
Mail list logo
