Hi

I need to copydb a 88591 table into a utf8 database.

I can see there is some plan for Ingres/Actian to support a copydb -
nvarchar option to support conversion to utf8

My assumption is that an varchar with extended chars eg Áé
copydb -c -nvarchar will generate datafile such that the number of
characters in utf8 (greater number of chars) will successfully copy in
to a utf8 database.

What version of Ingres will support the -nvarchar flag?

Thanks

On Oct 2, 10:19*pm, seldom isnice <seldomisnice... (AT) gmail (DOT) com> wrote:
PS I refer to this

Project Name UTF8 Portable COPYDB & UNLOADDB
Author Alex Hanshaw
Last Saved Date April 18th 2011

Hi seldom

I believe you need an Ingres10.

Martin Bowes

-----Original Message-----
From: seldom isnice [mailto:seldomisnice248 (AT) gmail (DOT) com]
Sent: 02 October 2011 22:20
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] Ingres version to support copydb -nvarchar

Hi

I need to copydb a 88591 table into a utf8 database.

I can see there is some plan for Ingres/Actian to support a copydb -
nvarchar option to support conversion to utf8

My assumption is that an varchar with extended chars eg Áé
copydb -c -nvarchar will generate datafile such that the number of
characters in utf8 (greater number of chars) will successfully copy in
to a utf8 database.

What version of Ingres will support the -nvarchar flag?

Thanks
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

I should also have said I recently used the Ingres10 copydb -nvarchar to achieve a transfer from an ISO88591 installation to a UTF8 Installation (Vectorwise).

It ran like a dream.

Marty

-----Original Message-----
From: Martin Bowes [mailto:martin.bowes (AT) ctsu (DOT) ox.ac.uk]
Sent: 03 October 2011 08:19
To: Ingres and related product discussion forum
Cc: seldom isnice
Subject: Re: [Info-Ingres] Ingres version to support copydb -nvarchar

Hi seldom

I believe you need an Ingres10.

Martin Bowes

-----Original Message-----
From: seldom isnice [mailto:seldomisnice248 (AT) gmail (DOT) com]
Sent: 02 October 2011 22:20
To: info-ingres (AT) kettleriverconsulting (DOT) com
Subject: [Info-Ingres] Ingres version to support copydb -nvarchar

Hi

I need to copydb a 88591 table into a utf8 database.

I can see there is some plan for Ingres/Actian to support a copydb -
nvarchar option to support conversion to utf8

My assumption is that an varchar with extended chars eg Áé
copydb -c -nvarchar will generate datafile such that the number of
characters in utf8 (greater number of chars) will successfully copy in
to a utf8 database.

What version of Ingres will support the -nvarchar flag?

Thanks
_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres


_______________________________________________
Info-Ingres mailing list
Info-Ingres (AT) kettleriverconsulting (DOT) com
http://ext-cando.kettleriverconsulti...fo/info-ingres

On 10/3/2011 1:19 AM, Martin Bowes wrote:
What are the conditions that this will work? Does this only work from
one ISO88591 installation to another ISO88591 installation?

I tried this from a SHIFTJIS installation to another SHIFTJIS
installation and failed with a GCA protocol service failure.

I tried this from a UTF8 installation against a SHIFTJIS installation
and not surprisingly got the "couldn't negotiate character content"
message.

It seems to only work from an ISO88591 installation to another ISO88591
installation.

All of my attempts were using a vnode to a remote installation.

Dennis

Hi Dennis et al,

I've used it successfully between ISO88591 and UTF8. However as you note you cannot use a vnode between these installations as they will not negotiate a charcter set. So on the ISO88591 installation I ran the copydb -nvarchar, then moved the files to the UTF8 installation where they were uploaded into a database created with the -i flag.

I'd be surprised if you need this flag to get a copy between two SHIFTJIS installations but the GCA message troubles me. I take it that the vnode you were using is functional. If no other good reason presents itself, I'd report the problem to IngresCorp.

Marty

On 10/4/2011 2:14 AM, Martin Bowes wrote:

Hi Marty,

Yes, the SHIFTJIS vnode is functional using isql, for example. The
copydb ... part works, but when running sql vnode::dbName < copy.out is
when the error happens.

Dennis

On 10/4/2011 7:28 AM, Dennis wrote:
As a test I copied a remote SHIFTJIS installation table data into a
local Ingres10 SHIFTJIS installation, thinking the issue may be Ingres10
trying to talk to an earlier version of Ingres in certain situations.

After creating the copy.out script with copydb -c -nvarchar... on the
local Ingres10 SHIFTJIS installation, then running the copy.out script,
any row that had a column with SHIFTJIS characters failed with a
"couldn't convert to row format..." message.

Dennis