I have been following this on and off. I don't have much to add to the specific problem, but I do have some general thoughts that may help.
I. It seems to be a similar (not same, and even similar may be a stretch) problem to the parameter formating problem 'solved' by .paramstyle which is one of the worst solutions I have seen to any problem :) to me, the parameter problem should be solved "in" the db-api layer, not above it (assuming application is above database.) Again, I agree that the type problem is not the same as parameter, so it may need a different solution that will have similarities to what I dislike about .paramstyle. II. (going out on a limb here...) A user defined data type is used (therefor defined) by the application, so it makes perfect sense that the app layer would have implementation details. If the person defining the datatype wants to use it across applications, then they will code an appropriate class. I can't see how a user defined anything can be handled generically. Carl K _______________________________________________ DB-SIG maillist - DB-SIG@python.org http://mail.python.org/mailman/listinfo/db-sig
