Re: [DB] returning typed data when fetching rows

Paul M Jones wrote:

Guillaume, do you think an add-on to DB_Table would be useful in this case? If so, write up a patch and we can work on incorporating it.

Well, that's my problem: I'm still a bit lost, with all those different implementations. Once I know what which class should be patched, I will have no problem writing a patch that integrates well.

But I must agree with regard to supporting the "array" data type; I don't think the PEAR abstraction libraries can reasonably be expected to handle them all. E.g., I think PG has a "geo" data type for latitude/longitude coordinates; in the same manner MySQL has its own special types (enum, set).

Why not? So if I need to use even just one proprietary feature, why do I have to hack it myself? Isn't PEAR about making developers' job easier by providing high quality code? I probably wouldn't have considered using pg arrays if MusicBrainz hadn't used them in their database: http://www.musicbrainz.org/ I believe that proprietary features should be supported by abstraction layers, provided that the developer is informed that it is, in fact, proprietary, and that this particular portion of code won't be easily portable. I don't expect it from a 1.0 version, but DB and the likes are already quite mature now, aren't they?