FWD:DBD.Ingres 0.51 unicode support

FWD:DBD.Ingres 0.51 unicode support

am 05.02.2007 14:05:11 von viktor.huebner

------_=_NextPart_001_01C74926.79C237CD
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Von: Viktor Hübner
Gesendet: Mo 05.02.2007 13:58
An: htoug@cpan.org
Betreff: DBD.Ingres 0.51 unicode support
=20
Hi,

sorry if this is the wrong address for my question, but I have not find =
related information on other way. I have a problem with DBD.Ingres 0.51 =
on SuSE Linux 9.0 with DB Ingres II 3.0.3 (int. lnx. 103). Are the =
unicode types (nvarchar/nchar) not supported in this version?
An error message is shown =93filed has unsupported type 27=94 =
if access a table with nvarchar. Have you any idea what can be this =
problem solved?

Regards,=20
Viktor Huebner

Senior Consultant
Merkantis Business Solutions GmbH
Menkestraße 7
D-26419 Schortens

Call: +49(0)44 61 / 7436-13
Fax: +49(0)44 61 / 7436- 29
Mobil: 0175-7222-312
Email: viktor.huebner@merkantis.de
Internet: www.merkantis.de



------_=_NextPart_001_01C74926.79C237CD--

Re: DBD.Ingres 0.51 unicode support

am 07.02.2007 10:57:48 von htoug

Viktor Hübner wrote:
> sorry if this is the wrong address for my question, but I have not
> find related information on other way. I have a problem with
> DBD.Ingres 0.51 on SuSE Linux 9.0 with DB Ingres II 3.0.3 (int. lnx.
> 103). Are the unicode types (nvarchar/nchar) not supported in this
> version?
> An error message is shown “filed has unsupported
> type 27” if access a table with nvarchar. Have you any idea what can
> be this problem solved?

Hi.

This is the corect place for this kind of question.

Unfortunately you are quite right - the current release of DBD::Ingres
does not support wide (unicode) character sets.

As far as I can recall it should not be too difficult to add, but I
haven't got round to it yet.
And as I no longer use Ingres actively (I have switched jobs over a year
ago and now have to suffer under MySQL) the chances that I will add it
in the near furture are very slim.

You are more than welcome to patch it yourself. I will be happy to
release a new version or add you as a co-maintainer of DBD::Ingres.

Best of luck and sorry I cannot be more helpful

--
Henrik Tougaard, no longer the active maintainer of DBD::Ingres.

Re: DBD.Ingres 0.51 unicode support

am 07.02.2007 11:23:00 von Alexander

Perhaps my Unicode patch for DBD::ODBC (at
http://www.alexander-foken.de/downloads.html) could show a way how to
modify DBD::Ingres. Someone could also try to make my changes to
DBD::ODBC work on non-Win32 platforms.

Alexander

On 07.02.2007 10:57, Henrik Tougaard wrote:
> Viktor Hübner wrote:
>> sorry if this is the wrong address for my question, but I have not
>> find related information on other way. I have a problem with
>> DBD.Ingres 0.51 on SuSE Linux 9.0 with DB Ingres II 3.0.3 (int. lnx.
>> 103). Are the unicode types (nvarchar/nchar) not supported in this
>> version? An error message is shown “filed has unsupported
>> type 27” if access a table with nvarchar. Have you any idea what can
>> be this problem solved?
>
> Hi.
>
> This is the corect place for this kind of question.
>
> Unfortunately you are quite right - the current release of DBD::Ingres
> does not support wide (unicode) character sets.
>
> As far as I can recall it should not be too difficult to add, but I
> haven't got round to it yet.
> And as I no longer use Ingres actively (I have switched jobs over a
> year ago and now have to suffer under MySQL) the chances that I will
> add it in the near furture are very slim.
>
> You are more than welcome to patch it yourself. I will be happy to
> release a new version or add you as a co-maintainer of DBD::Ingres.
>
> Best of luck and sorry I cannot be more helpful
>
> --
> Henrik Tougaard, no longer the active maintainer of DBD::Ingres.


--
Alexander Foken
mailto:alexander@foken.de http://www.foken.de/alexander/

Unicode patch for DBD::ODBC (was: DBD.Ingres 0.51 unicode support)

am 07.02.2007 12:45:30 von henning.just

Excuse me if I have misunderstood something here - but that patch looks =
like something I have been looking for for some time. I just checked the =
svn repository for DBD::ODBC (at =
http://svn.perl.org/modules/dbd-odbc/trunk) and couldn't see your =
changes there. Have you sent the patch to Urlwin?

Anyway, thank you for your work, I'll be trying it out shortly.


Best regards
Henning Michael M=F8ller Just



-----Original Message-----
From: Alexander Foken [mailto:alexander@foken.de]=20
Sent: Wednesday, February 07, 2007 11:23 AM
To: htoug@cpan.org; Viktor Hübner; dbi-users@perl.org
Subject: Re: DBD.Ingres 0.51 unicode support

Perhaps my Unicode patch for DBD::ODBC (at=20
http://www.alexander-foken.de/downloads.html) could show a way how to=20
modify DBD::Ingres. Someone could also try to make my changes to=20
DBD::ODBC work on non-Win32 platforms.

Alexander

RE: DBD.Ingres 0.51 unicode support

am 09.02.2007 14:13:22 von Grant.Croker

> -----Original Message-----
> From: Henrik Tougaard [mailto:htoug@cpan.org]
> Sent: 07 February 2007 10:58
> To: Viktor Hübner
> Cc: dbi-users@perl.org
> Subject: Re: DBD.Ingres 0.51 unicode support
>=20
> Viktor Hübner wrote:
> > sorry if this is the wrong address for my question, but I have not
> > find related information on other way. I have a problem with
> > DBD.Ingres 0.51 on SuSE Linux 9.0 with DB Ingres II 3.0.3 (int. lnx.
> > 103). Are the unicode types (nvarchar/nchar) not supported in this
> > version?
> > An error message is shown "filed has unsupported
> > type 27" if access a table with nvarchar. Have you any idea what can
> > be this problem solved?
>=20
> Hi.
>=20
> This is the corect place for this kind of question.
>=20
> Unfortunately you are quite right - the current release of DBD::Ingres
> does not support wide (unicode) character sets.
>=20
> As far as I can recall it should not be too difficult to add, but I
> haven't got round to it yet.
> And as I no longer use Ingres actively (I have switched jobs over a =
year
> ago and now have to suffer under MySQL) the chances that I will add it
> in the near furture are very slim.
>=20
> You are more than welcome to patch it yourself. I will be happy to
> release a new version or add you as a co-maintainer of DBD::Ingres.
>=20
> Best of luck and sorry I cannot be more helpful

Hi Henrik,

I have managed to get Unicode fetches to work with Ingres. See =
http://ingres.co.uk/files/perl/unicode/dbd-ingres-unicode-fe tch.patch =
for the patch (generated using diff -u).

It has been tested on Windows XP as well as a 64 bit Linux system. If =
you feel it should be tested on another platform let me know.

My test case (http://ingres.co.uk/files/perl/unicode/unicode-ingres.txt) =
uses the demodb database that is shipping with Ingres 2006 R2. Should =
you or anyone want to get a copy of this data and the schema please =
email me.

Regards

grant

Re: DBD.Ingres 0.51 unicode support

am 09.02.2007 14:26:49 von Tim.Bunce

On Fri, Feb 09, 2007 at 08:13:22AM -0500, Grant Croker wrote:
> > -----Original Message-----
> > From: Henrik Tougaard [mailto:htoug@cpan.org]
> > Sent: 07 February 2007 10:58
> > To: Viktor Hübner
> > Cc: dbi-users@perl.org
> > Subject: Re: DBD.Ingres 0.51 unicode support
> >
> > Viktor Hübner wrote:
> > > sorry if this is the wrong address for my question, but I have not
> > > find related information on other way. I have a problem with
> > > DBD.Ingres 0.51 on SuSE Linux 9.0 with DB Ingres II 3.0.3 (int. lnx.
> > > 103). Are the unicode types (nvarchar/nchar) not supported in this
> > > version?
> > > An error message is shown "filed has unsupported
> > > type 27" if access a table with nvarchar. Have you any idea what can
> > > be this problem solved?
> >
> > Hi.
> >
> > This is the corect place for this kind of question.
> >
> > Unfortunately you are quite right - the current release of DBD::Ingres
> > does not support wide (unicode) character sets.
> >
> > As far as I can recall it should not be too difficult to add, but I
> > haven't got round to it yet.
> > And as I no longer use Ingres actively (I have switched jobs over a year
> > ago and now have to suffer under MySQL) the chances that I will add it
> > in the near furture are very slim.
> >
> > You are more than welcome to patch it yourself. I will be happy to
> > release a new version or add you as a co-maintainer of DBD::Ingres.
> >
> > Best of luck and sorry I cannot be more helpful
>
> Hi Henrik,
>
> I have managed to get Unicode fetches to work with Ingres. See
> http://ingres.co.uk/files/perl/unicode/dbd-ingres-unicode-fe tch.patch
> for the patch (generated using diff -u).
>
> It has been tested on Windows XP as well as a 64 bit Linux system. If
> you feel it should be tested on another platform let me know.
>
> My test case
> (http://ingres.co.uk/files/perl/unicode/unicode-ingres.txt) uses the
> demodb database that is shipping with Ingres 2006 R2. Should you or
> anyone want to get a copy of this data and the schema please email me.

It's important that users are not burdened with having to add decode("UTF-16LE", ...)
all over their code.

It's expected that drivers return non-iso-8859-1 character data as utf8
in scalars with the SvUTF8 flag set.

I see that the DBI docs don't mention that explicitly, so I'm adding it now.

Any driver not doing that is arguably broken, or at least painful to use
and the application is unlikely to port to other drivers easily.

Tim.

RE: DBD.Ingres 0.51 unicode support

am 12.02.2007 15:30:24 von Grant.Croker

> -----Original Message-----
> From: Tim Bunce [mailto:Tim.Bunce@pobox.com]
> Sent: 09 February 2007 14:27
> To: Grant Croker
> Cc: htoug@cpan.org; dbi-users@perl.org; Viktor Hübner
> Subject: Re: DBD.Ingres 0.51 unicode support
>=20
>=20
> It's important that users are not burdened with having to add =
decode("UTF-
> 16LE", ...)
> all over their code.
>=20
> It's expected that drivers return non-iso-8859-1 character data as =
utf8
> in scalars with the SvUTF8 flag set.
>=20
> I see that the DBI docs don't mention that explicitly, so I'm adding =
it
> now.
>=20
> Any driver not doing that is arguably broken, or at least painful to =
use
> and the application is unlikely to port to other drivers easily.
>=20
> Tim.

Hi Tim,

Thanks for the feedback - I will see about getting it corrected

Regards

grant