Bug #43063 for POE-Component-SimpleDBI: feature request: better utf 8 support through ENCODING or ATTRIBUTE argument in SimpleDBI::CONNECT

Thu Feb 05 14:29:34 2009 sean.pieper [...] viable.net - Ticket created

Subject:	feature request: better utf 8 support through ENCODING or ATTRIBUTE argument in SimpleDBI::CONNECT
Date:	Thu, 5 Feb 2009 14:01:11 -0500 (EST)
To:	bug-POE-Component-SimpleDBI [...] rt.cpan.org
From:	sean.pieper [...] viable.net

Hi, I'm working with a UTF-8 encoded postgres DB, and would like to be able to properly read wide characters. DBD::Pg has a DB handle attribute pg_enable_utf8 that would solve my problems, but DBISimple doesn't provide an easy way for me to specify driver specific attributes this during connection. The most obvious solution seems to be expanding CONNECT to take either: ATTRIBUTES=>{pg_enable_utf8 => 1, pg_specific_crud =>0} and letting the DBD module do the work, or, ENCODING=>"utf8" and then calling decode() as appropriate on SINGLE and MULTIPLE operations. Thanks, -sean This e-mail, including any attachments may contain information that is protected by law as PRIVILEGED AND CONFIDENTIAL and is intended solely for the use of the recipient or the employee or agent responsible for delivering the message to the recipient. Please note that if you are not the intended recipient, you are hereby notified that any dissemination, copying, distribution, retention, re-transmission, printing or any other use of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail communication in error, please immediately send an e-mail reply to notify the sender and immediately and permanently delete this e-mail from your computer system. Thank you.

Tue Jun 16 16:21:23 2009 mdorman [...] ironicdesign.com - Correspondence added 5 min

Show quoted text

> I'm working with a UTF-8 encoded postgres DB, and would like to be > able to properly read wide characters. DBD::Pg has a DB handle > attribute pg_enable_utf8 that would solve my problems, but > DBISimple doesn't provide an easy way for me to specify driver > specific attributes this during connection.

Hey, Sean, You can already do this. in the DBI connect string, just do: DBI:Pg(pg_enable_utf8=>1):host=foo;dbname=bar It's a standard part of the DBI (look for "connection attribute values" in the man page) and as far as my testing goes, appears to work just fine. Mike.

Tue Jun 16 16:21:24 2009 The RT System itself - Status changed from 'new' to 'open'

Tue Jun 16 16:33:06 2009 sean.pieper [...] viable.net - Correspondence added

Subject:	RE: [rt.cpan.org #43063] feature request: better utf 8 support through ENCODING or ATTRIBUTE argument in SimpleDBI::CONNECT
Date:	Tue, 16 Jun 2009 16:32:47 -0400 (EDT)
To:	bug-POE-Component-SimpleDBI [...] rt.cpan.org
From:	sean.pieper [...] viable.net

ahh, cool. I knew it was an available attribute, but didn't realize it could be popped right into the connection string itself. Thank you :-). -sean Show quoted text

-----Original Message----- From: "Michael Alan Dorman via RT" <bug-POE-Component-SimpleDBI@rt.cpan.org> Sent: Tuesday, June 16, 2009 4:21pm To: sean.pieper@viable.net Subject: [rt.cpan.org #43063] feature request: better utf 8 support through ENCODING or ATTRIBUTE argument in SimpleDBI::CONNECT <URL: https://rt.cpan.org/Ticket/Display.html?id=43063 >

> I'm working with a UTF-8 encoded postgres DB, and would like to be > able to properly read wide characters. DBD::Pg has a DB handle > attribute pg_enable_utf8 that would solve my problems, but > DBISimple doesn't provide an easy way for me to specify driver > specific attributes this during connection.

Hey, Sean, You can already do this. in the DBI connect string, just do: DBI:Pg(pg_enable_utf8=>1):host=foo;dbname=bar It's a standard part of the DBI (look for "connection attribute values" in the man page) and as far as my testing goes, appears to work just fine. Mike. Sean Pieper Engineer Viable, Inc. VRS: ViableVRS.tv www.viable.net sean.pieper@viable.net Office: 240-292-0222 x244 VSN: viablepieper This e-mail, including any attachments may contain information that is protected by law as PRIVILEGED AND CONFIDENTIAL and is intended solely for the use of the recipient or the employee or agent responsible for delivering the message to the recipient. Please note that if you are not the intended recipient, you are hereby notified that any dissemination, copying, distribution, retention, re-transmission, printing or any other use of this e-mail or the information contained herein is strictly prohibited. If you have received this e-mail communication in error, please immediately send an e-mail reply to notify the sender and immediately and permanently delete this e-mail from your computer system. Thank you.

Wed Nov 05 17:19:59 2014 APOCAL [...] cpan.org - Correspondence added

Hello, I've just uploaded v1.31 that includes a note which explains how to add custom attributes. Thanks :) -- ~Apocalypse

Wed Nov 05 17:20:00 2014 APOCAL [...] cpan.org - Status changed from 'open' to 'resolved'