Ticket #2589 (closed bug: duplicate)

Opened 3 years ago

Last modified 3 years ago

DB input bug

Reported by: drziko Owned by: nobody
Priority: major: does not work as expected Milestone: Version 1.5.0
Component: Data Provider Version: 1.4.0
Keywords: Cc:
Platform Version: Platform: Windows
Must Fix for Release: Yes Awaiting user input: yes

Description

I have a PostGis? server on ubuntu. Also i have a some clients on Windows (XP and Vista). When I make one polygon all is ok, but if I make 2 or more polygons and afret that try to save a layer a have a error:

"ERROR:  character 0xc390 of encoding "UTF8" has no equivalent in "WIN1251"".

It's message from DB server. DB has a windows-1251 charset now. I have this error form ubuntu and from Windows boarded PC.

Change History

  Changed 3 years ago by drziko

  • component changed from Build/Install to Data Provider

Change a component

follow-up: ↓ 3   Changed 3 years ago by jef

  • status_info set

everytime or just when you enter certain characters in the attributes? Can you give an example of the data you enter? Are there default values on the postgresql tables?

in reply to: ↑ 2   Changed 3 years ago by drziko

Replying to jef:

everytime or just when you enter certain characters in the attributes? Can you give an example of the data you enter? Are there default values on the postgresql tables?

It's happend when I enter certain characters in the attributes in Russian. If I enter in English - all is ok. Or if I create some polygons and don't fill attributes - all is ok too. The Postgress encoding is UTF-8. If I make encoding as CP1251, database give error, that can't write it. In UTF-8 this problem doesn't exist. In major default values give this error. Maybe it'll be better if I give you a screencast?

  Changed 3 years ago by drziko

 http://www.youtube.com/watch?v=YAJznwabluU - this is a screencast. I enter characters in attributes on Russian.

  Changed 3 years ago by jef

  • status changed from new to closed
  • resolution set to duplicate

duplicate of #2707

Note: See TracTickets for help on using tickets.