Return-Path: Received: from lists.mysql.com (lists2.mysql.com [213.136.52.31]) by pauline.vellum.cz (8.11.6/8.11.6) with SMTP id j5PFW9J08199 for ; Sat, 25 Jun 2005 17:32:09 +0200 Received: (qmail 25890 invoked by uid 510); 25 Jun 2005 15:31:57 -0000 Mailing-List: contact perl-help@lists.mysql.com; run by ezmlm List-ID: Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Archive: http://lists.mysql.com/perl/3564 Delivered-To: mailing list perl@lists.mysql.com Received: (qmail 25868 invoked by uid 509); 25 Jun 2005 15:31:57 -0000 Received-SPF: pass (listsnew.mysql.com: local policy) Date: Sat, 25 Jun 2005 11:27:38 -0400 (EDT) From: Rudy Lippan X-X-Sender: rlippan@elfride.ineffable.net To: Jan Kratochvil cc: perl@lists.mysql.com Subject: Re: [patch] DBD::mysql UTF-8 handling In-Reply-To: <20050625121615.GA8358@kashome.dyn.jankratochvil.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Content-Disposition: INLINE On Sat, 25 Jun 2005, Jan Kratochvil wrote: > yet another mail in the utf8 saga. > > Attached patch is just a followup to: > http://lists.mysql.com/perl/3006?f=plain > > but also implementing proper _writing_ of utf-8 data to MySQL. The patch above > worked fine for me for _reading_ but I was unable to find out any way how to > write them properly in utf-8. > But the patches don't make a distinction of binary vs. char types, ie. only char/varchar/text/&c. should be flagged as utf-8 whereas BLOBs and friends should be left alone, right? Or did I miss the code that does that, for I only did a cursory look over? -r -- MySQL Perl Mailing List For list archives: http://lists.mysql.com/perl To unsubscribe: http://lists.mysql.com/perl?unsub=lace@jankratochvil.net