-----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160
> I believe that this is a deficiency in DBD::Pg. Another deficiency is > in its inability to determine that a user-defined type should be > converted to utf8 when pg_enable_utf8 is set We're still waiting on your patch. ;) > At the very least, we need to find a way to let users tell DBD::Pg how > to handle certain types. DBD::Pg could then look up the appropriate > OIDs when it first connects and then store them. Right. I looked into this some time back, and made a rough proof of concept, but there was some big problem I ran into. Cannot remember at the moment what it was. <...ponders...> Oh right, I think it was just the complication that at the time you encounter an unknown type, you are already knee-deep in the middle of a fetch run, so making a separate call right then to the backend to ask it for information about that type is not possible. One solution would be to have a flag that makes DBD::Pg grab info about all custom types on startup (which has an associated cost). Another would be to have it abort the current fetch, grab the custom info, cache it, then re-run the query. A third would be to have a special command that you can run to have it grab the custom type information on demand. - -- Greg Sabino Mullane [email protected] End Point Corporation PGP Key: 0x14964AC8 200909081405 http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8 -----BEGIN PGP SIGNATURE----- iEYEAREDAAYFAkqmnNIACgkQvJuQZxSWSsiY1gCg5sHWGsQKruQdxbAF8LDiP0Dj kA8AnRnImkJBY2spgrknzyg70xikL0T0 =suIY -----END PGP SIGNATURE-----
