On Wed, 2005-08-31 at 10:29 -0400, Tom Lane wrote:
> Joost Kraaijeveld <[EMAIL PROTECTED]> writes:
> If, as seems more likely, there's a mishmash of different encodings then
> you are in for some pain. At the minimum you'll have to separate out
Yep. The original database (which is copied to an SQL-ASCII PostgreSQL
database) is a mishmash of encodings. Actually no official encoding is
given for the database.
But I managed to get an acceptable (for me that is) import, only losing
all the diacritical chars for this moment (see other mail)
Thanks for responding,
Joost.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
