Well, lets ask -hackers... When COPYing data from a file, the file encoding is taken from the client_encoding parameter. The JDBC driver always uses UNICODE as the client_encoding and wants to prevent people from changing it by monitoring ParameterStatus messages and erroring out if it's changed. This presents a problem when you want to COPY to or from a file with a different encoding. It seems reasonable to add an ENCODING specification to the COPY command instead of relying on the somewhat unrelated client_encoding setting. Oliver Jowett also noted that copying from a file with LATIN1 data into a table whose name contained UNICODE characters could not be done. Does this seem like a reasonable thing to do?
Kris Jurka On Mon, 8 Nov 2004, Barry Lind wrote: > I am assuming this will get addressed in the backend in 8.1 and that > would be the upgrade path. (I agree if there isn't agreement on the > server side that this is appropriate for the server, then this wouldn't > be the correct parameter). > > --Barry > ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster
