From: | Shivender Devarakonda <shivenderd(at)gmail(dot)com> |
---|---|
To: | Ader Javier <javierader(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Authentication failed when Password contains Japaneese Charecters |
Date: | 2010-04-21 05:44:54 |
Message-ID: | y2ka7ddbfcf1004202244ocd6ed49n6513ff1e9a65c5f8@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
I set the following property in postgresql.conf:
client_encoding = UTF-8 # actually, defaults to database
# encoding
I see the same problem after this also...
actaully my DB already shows the encoding format as UTF-8 so according to
the comments the client encoding should default to UTF-8.
Please let me know if I miss anything
Thanks,
Shivender
On Tue, Apr 20, 2010 at 9:10 PM, Ader Javier <javierader(at)gmail(dot)com> wrote:
> Try change the encoding of sesssions at database nivel to UTF8; this
> encoding is taked as default for sessions
> http://www.postgresql.org/docs/8.1/static/sql-alterdatabase.html ; try
> ALTER DATABASE databasename SET ENCODING TO 'UTF8'
> (or maybe UFT8 directly).
> or if this don't work try
> ALTER DATABASE databasename SET client_encoding TO 'UTF8'
> or.... from Java set the econding of connections on creation or
> configuration time (I don't know where exactly, but sure it's possible).
>
> Shivender Devarakonda escribió:
> >
> > When I did the psql -l I see the following DBs in my local environment:
> >
> > C:\PostgreSQL\bin>psql -l
> > List of databases
> > Name | Owner | Encoding
> > -----------+----------+-----------
> > cmdb | admin | UTF8
> > postgres | postgres | SQL_ASCII
> > template0 | postgres | SQL_ASCII
> > template1 | postgres | SQL_ASCII
> >
> > I am using cmdb which is UTF8.
> >
> > I think it is consistent with my application? any thoughts what might
> > be wrong.
> >
> > Thanks,
> > Shivender
> > On Tue, Apr 20, 2010 at 7:07 PM, Shivender Devarakonda
> > <shivenderd(at)gmail(dot)com <mailto:shivenderd(at)gmail(dot)com>> wrote:
> >
> > Thanks. Where should I look for this property?
> >
> > Thanks,
> > Shivender
> >
> >
> >
> >
> > On Tue, Apr 20, 2010 at 6:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us
> > <mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us>> wrote:
> >
> > Shivender Devarakonda <shivenderd(at)gmail(dot)com
> > <mailto:shivenderd(at)gmail(dot)com>> writes:
> > > I did not give any explicit encoding while creating the DB.
> > I am running
> > > postgres on Windows XP system.
> >
> > Well, you should look at what server_encoding is set to, then.
> > If it's not UTF-8 then that's likely the source of the problem.
> >
> > regards, tom lane
> >
> >
> >
>
>
>
> --
> Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-jdbc
>
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2010-04-21 14:41:25 | Re: SOLVED ... Re: Getting rid of a cursor from JDBC .... Re: [PERFORM] Re: HELP: How to tame the 8.3.x JDBC driver with a biq guery result set |
Previous Message | Ader Javier | 2010-04-21 04:10:36 | Re: Authentication failed when Password contains Japaneese Charecters |