On 03/03/11 09:18, Jasmin Dizdarevic wrote:
> @ALL: Isn't it possible and wise to include an (optional) encoder in pgsql?
>
> we're importing a lot of data from textfiles, which are not utf-8. we
> always have to change the encoding in another tool before using COPY.
SET client_encoding
--
Crai
@ALL: Isn't it possible and wise to include an (optional) encoder in pgsql?
we're importing a lot of data from textfiles, which are not utf-8. we always
have to change the encoding in another tool before using COPY.
2011/2/28 Craig Ringer
> On 27/02/11 20:47, AI Rumman wrote:
> > I am getting
On 27/02/11 20:47, AI Rumman wrote:
> I am getting error in Postgresql 9.0.1.
>
> update import_details_test
> set data_row = '["4","1 Monor JoÃ\u083ão S. AntÃ\u0083ão
^^
Because your email client may have transformed the text encod
On Feb 27, 2011, at 5:47 AM, AI Rumman wrote:
> Any idea please.
Don't do that ;-)
Seriously, the error means exactly what it says, so you have to figure out why
your app is trying to insert invalid UTF-8.
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 v
I am getting error in Postgresql 9.0.1.
update import_details_test
set data_row = '["4","1 Monor JoÃ\u083ão S. AntÃ\u0083ão (Schools
21,22,76)( Ru)","http://www.asdas.aa.nj.us","","908 436
4861","","","--None--","",","","--None--","","","0","","--None--","0","2008-12-29
17:53:08","","2010-08-2
