Just a thought: I think that Greg is right that the overhead is too much for every run, esp. when 99% of the apps out there won't need it but I still would find this very useful.
I would be willing to help where I can. I am not a C programmer so my expertise would be limited to the Perl component (or let me put it another way: you don't want my C code in your library). If there are other ways to help, I would be glad to do so. Anyway-- thoughts on this: Most apps should be able to get by specifying what custom types they need to know. It is not clear from Greg's email if this is the case, but it would seem to me that the function to learn the types should be one which allows specifying specific types, which could then be looked up in advance. Also another option has occurred to me-- that it might be better just to move this out of DBD::Pg and have another Perl library which allows for this parsing. In this case. However, before I add such capabilities to my application I would want to ensure that the behavior in DBD::Pg is stable (the improved array handling broke LSMB prerelease versions for a while). Best Wishes, Chris Travers
