Edgewall Software
Modify

Opened 19 years ago

Closed 18 years ago

#2538 closed enhancement (invalid)

client_encoding in postgresql

Reported by: ilia_kantor Owned by: Jonas Borgström
Priority: normal Milestone:
Component: timeline Version: 0.9.2
Severity: normal Keywords: postgresql
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description (last modified by Christopher Lenz)

The ticket refers to postgresql, didn't test it with sqlite.

Sometimes files have other encoding then UTF8. If that happens, timeline doesn't work, probably other trac modules.

To fix that, I added a 2 lines line to db.py

--- after ---
            cnx = PgSQL.connect('', user, password, host, path,port)
--- add this --- 
            cnx.cursor().execute('SET CLIENT_ENCODING TO \'win\';')
            cnx.commit()

--- end ---

I suggest to add client_encoding parameter to trac.ini (database setting ?)

Attachments (0)

Change History (2)

comment:1 by Christopher Lenz, 19 years ago

Description: modified (diff)

The encoding of files in the version control repository has nothing to do with encoding over the database connection… the files are not read from the DB. Please provide specifics about the actual problem you're seeing, I think you may have jumped to the wrong conclusion here.

comment:2 by Christian Boos, 18 years ago

Keywords: postgresql added
Resolution: invalid
Status: newclosed

Since there's been no feedback since 9 months, I think we can close this.

If there's any real issue with CLIENT_ENCODING and postgres, please reopen and document precisely what's going wrong and the steps to reproduce the error.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain Jonas Borgström.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from Jonas Borgström to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.