Jeff Amiel wrote:
> Ahhh
> *looks at encoding*
>
> Well..they are both the same...BUT...they are set to
> ENCODING = 'SQL_ASCII';
>
> That explains a lotthey should probably be set to Unicode UTF8
> Duh
>
> Any way to change encoding without dumping/restoring database?
You can
--- On Mon, 10/6/08, Scott Marlowe <[EMAIL PROTECTED]> wrote:
> I'm wondering if the OP has some line breaks in his
> data that are
> getting misinterpreted, or maybe his encoding on the two
> dbs is
> different and he's not taking care of that.
Ahhh
*looks at encoding*
Well..they are both
On Oct 6, 2008, at 10:11 AM, Scott Marlowe wrote:
On Mon, Oct 6, 2008 at 8:40 AM, ries van Twisk <[EMAIL PROTECTED]> wrote:
On Oct 6, 2008, at 9:11 AM, Jeff Amiel wrote:
I performed a pg_dump on a database and created a new schema-only
database
to copy that data into.
However trying to
On Mon, Oct 6, 2008 at 8:40 AM, ries van Twisk <[EMAIL PROTECTED]> wrote:
>
> On Oct 6, 2008, at 9:11 AM, Jeff Amiel wrote:
>
>>
>> I performed a pg_dump on a database and created a new schema-only database
>> to copy that data into.
>>
>> However trying to use psql -f to load the data in, I get a
On Oct 6, 2008, at 9:11 AM, Jeff Amiel wrote:
I performed a pg_dump on a database and created a new schema-only
database to copy that data into.
However trying to use psql -f to load the data in, I get a plethora
of syntax errors including the dreaded "invalid command \N".
I even tried
I performed a pg_dump on a database and created a new schema-only database to
copy that data into.
However trying to use psql -f to load the data in, I get a plethora of syntax
errors including the dreaded "invalid command \N".
I even tried to pipe the pg_dump results directly into the psql co
