Re: Dumping/Restoring with constraints? - Mailing list pgsql-general

From Phoenix Kiula
Subject Re: Dumping/Restoring with constraints?
Date
Msg-id e373d31e0808282253o13844c76odcd6f118fef4ff2e@mail.gmail.com
Whole thread Raw
In response to Re: Dumping/Restoring with constraints?  (Andrew Sullivan <ajs@commandprompt.com>)
Responses Re: Dumping/Restoring with constraints?  (Andrew Sullivan <ajs@commandprompt.com>)
List pgsql-general
On 8/29/08, Andrew Sullivan <ajs@commandprompt.com> wrote:
>
> The latter should be in effect if your database encoding is UTF-8.
>  What's the database encoding?


My database encoding on BOTH the sides is UTF8. The dumped DB is UTF8.
The one I am importing into is also UTF8. So why is it showing me this
error? Do I also have to look at stuff like "collation"?

Also, how can I ensure that my dumped database on the server has only
UTF8 data? What constraint or function can I use?

Thanks

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: MySQL LAST_INSERT_ID() to Postgres
Next
From: Giorgio Valoti
Date:
Subject: [Semi-OT]: How to customize locales?