Re: [PyIndexer] Representing MySQL results as native data types

[Chris W. <ch...@ni...>]

Marcus Collins wrote:
> 
> I think it's probably implemented like this because returning it as a
> string is the most universal 

Yeah, I think I actually see why it needs to be like that back now, just a shame
we need to take the implicit performacne hit...

> However, it would indeed be good to see the C API support the data types
> C knows about natively -- and these do account for the majority of
> MySQL's native data types. It would be interesting to determine what it
> would take to add this.

That sounds like a question for the MySQL lists ;-)

<snip>
> to examine the column type, treat the binary data appropriately, and
> return a native Python object of the appropriate type.

That would be cool, if I understood it entirely... I got the native Python
object bit :-S

cheers,

Chris