Received: by 10.101.3.11 with SMTP id f11mr4469272ani.26.1337031749791;
        Mon, 14 May 2012 14:42:29 -0700 (PDT)
X-BeenThere: golang-nuts@googlegroups.com
Received: by 10.236.114.50 with SMTP id b38ls15755990yhh.1.gmail; Mon, 14 May
 2012 14:42:20 -0700 (PDT)
Received: by 10.236.46.101 with SMTP id q65mr512659yhb.20.1337031740404;
        Mon, 14 May 2012 14:42:20 -0700 (PDT)
Date: Mon, 14 May 2012 14:42:19 -0700 (PDT)
From: Julien Schmidt <g...@julienschmidt.com>
To: golang-nuts@googlegroups.com
Message-ID: <21614981.962.1337031739594.JavaMail.geo-discussion-forums@ynia9>
In-Reply-To: <16790eff-f021-414a-89de-c2079b8c052d@m10g2000vbn.googlegroups.com>
References: <CAHDOXNhMybOU1AMgzTPq1+a9P=e4__fo5y+qYoK9Su+owuUwgw@mail.gmail.com>
 <24095261.289.1336569980213.JavaMail.geo-discussion-forums@ynmc31>
 <16790eff-f021-414a-89de-c2079b8c052d@m10g2000vbn.googlegroups.com>
Subject: Re: mysql
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_960_30869801.1337031739593"

------=_Part_960_30869801.1337031739593
Content-Type: multipart/alternative; 
	boundary="----=_Part_961_10123316.1337031739594"

------=_Part_961_10123316.1337031739594
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Last time i took a look at your source was definitely before v4.6a. Do you 
handle time values (both as driver.Value and as packet) well?

On Monday, May 14, 2012 11:15:10 PM UTC+2, ziutek wrote:
>
> On 9 Maj, 15:26, Julien Schmidt <g...@julienschmidt.com> wrote: 
> > I guess in some cases its even more stable than mymysql, since mymysql 
> does 
> > not handle all input types and mysql packet types. 
>
> mymysql handles all types since v4.6a. There were three unhandled 
> types before v4.2.3 and two before v4.6a (there were forgotten TODO 
> for them in type handling code). 
>
> Can you write more details about unhandled packet types you found in 
> mymysql?


------=_Part_961_10123316.1337031739594
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

Last time i took a look at your source was definitely before v4.6a. Do you handle time values (both as driver.Value and as packet) well?<div><br>On Monday, May 14, 2012 11:15:10 PM UTC+2, ziutek wrote:<blockquote class="gmail_quote" style="margin: 0;margin-left: 0.8ex;border-left: 1px #ccc solid;padding-left: 1ex;">On 9 Maj, 15:26, Julien Schmidt &lt;<a>g...@julienschmidt.com</a>&gt; wrote:
<br>&gt; I guess in some cases its even more stable than mymysql, since mymysql does
<br>&gt; not handle all input types and mysql packet types.
<br>
<br>mymysql handles all types since v4.6a. There were three unhandled
<br>types before v4.2.3 and two before v4.6a (there were forgotten TODO
<br>for them in type handling code).
<br>
<br>Can you write more details about unhandled packet types you found in
<br>mymysql?</blockquote></div>
------=_Part_961_10123316.1337031739594--

------=_Part_960_30869801.1337031739593--