We have solved the problem. Maybe someone will face the same problem so
just to close this thread, the problem was in php.ini where a default
output character set was set which caused the "second" recoding problem
(just for display using php).
Miroslav Åulc wrote:
Hi all,
I have problem on one
On Mar 16, 2005, at 9:34 AM, Miroslav Šulc wrote:
I have problem on one of our potentional client's linux server with
data encoding. I have played with this for some time but with no
success. Here is the problem:
Maybe try setting the client side encoding explicitly at the top of the
dump file:
John DeSoi wrote:
On Mar 16, 2005, at 9:34 AM, Miroslav Šulc wrote:
I have problem on one of our potentional client's linux server with
data encoding. I have played with this for some time but with no
success. Here is the problem:
Maybe try setting the client side encoding explicitly at the top
Just update - the system is Fedora Core 2, but the PostgreSQL is
compiled from sources.
Miroslav Åulc wrote:
Hi all,
I have problem on one of our potentional client's linux server with
data encoding. I have played with this for some time but with no
success. Here is the problem:
I have dump fi
Hi all,
I have problem on one of our potentional client's linux server with data
encoding. I have played with this for some time but with no success.
Here is the problem:
I have dump file created with pg_dump on my dev linux machine
(PostgreSQL 8.0.1). When I upload the file to the client's ser
