|
Re: COPY support in pgsql-jdbc driver: msg#00174db.postgresql.jdbc
Sam Varshavchik wrote: Barry Lind writes: True, but if you want to look at the data in an editor you might like it to be in a character set you can view, also if you are going to reload the data through a different client (i.e. psql) you won't easily be able to as it will assume the client encoding. I said earlier that if the client encoding = server encoding this should be a noop. So you would always have the ability to have a higher level of performance by specifying the same encoding as the server. I also suggested that there be a method that didn't take an encoding which would use a default encoding. My recomendation was that the default be the default encoding for the running jvm, but it could default to the same encoding as the server. However since all the jdk methods that I am aware of which have an optional encoding argument default to the jvm encoding, I think it would be confusing to do something different here. But I could be convinced otherwise. thanks, --Barry ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: COPY support in pgsql-jdbc driver: 00174, Sam Varshavchik |
|---|---|
| Next by Date: | referential integrity violation makes connection pool useless: 00174, Craig Moon |
| Previous by Thread: | Re: COPY support in pgsql-jdbc driveri: 00174, Sam Varshavchik |
| Next by Thread: | Re: COPY support in pgsql-jdbc driver: 00174, Michael Adler |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |