Обсуждение: SQL Server to Postgres Migration

Greetings,

I've found a problem with the Database Migration Wizard.  When porting SQL
Memo fields to Postgres Text fields, hard returns are replaced with one
of:  chr(13), chr(13)||chr(10), or chr(10)||chr(13).  However, when
entering new data into a text field, a hard return is entered as chr(10).
The result of the porting is that the fields or the entire record is
rendered uneditable through ADO code.  The records can be changed with
pgAdmin II though.

Corin Froese
Application Developer
Sorex Software Inc.
corin@sorexsoftware.com

> -----Original Message-----
> From: Corin Froese [mailto:corin@sorexsoftware.com]
> Sent: 28 August 2002 20:42
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] SQL Server to Postgres Migration
>
>
> Greetings,
>
> I've found a problem with the Database Migration Wizard.
> When porting SQL Memo fields to Postgres Text fields, hard
> returns are replaced with one
> of:  chr(13), chr(13)||chr(10), or chr(10)||chr(13).
> However, when entering new data into a text field, a hard
> return is entered as chr(10).
> The result of the porting is that the fields or the entire
> record is rendered uneditable through ADO code.  The records
> can be changed with pgAdmin II though.

Umm, pgAdmin does it through ADO :-)

Seriously though, pgAdmin doesn't edit the data in memo fields in any
way, other than to replace \ with \\ and ' with '' just to ensure that a
valid SQL query is generated (it does fiddle with dates, times and
booleans, just to iron out any regional formatting quirks). The data is
selected from the source database into an ADO recordset, which is
iterated through, generating an INSERT query for each record which is
then executed using ADO again.

What can't you edit the data with?

Regards, Dave.