John Stanton wrote: > The method I wrote about earlier is part of a language binding. > I can show you the code if you are interested.
I think we must be talking about different things, then. A language binding that allows the user to write their own SQL cannot automatically insert cast() calls into the queries without parsing the SQL and making a runtime determination about the context in which each bound parameter will be evaluated. And that's the halting problem. :) Maybe you're talking about something like rails, which abstracts away the SQL from the user API and generates its own queries? Then sure. But that's not the level of abstraction I'm working with. But regardless: sure, I'd be curious to see how you are dealing with the same issue. What I've done for now is just change the default from bind_blob() to bind_text(), and add some language to the docs warning users that they need to add a cast-to-text when writing expressions involving blob columns. Since comparing blob values is obviously rare, this seems to me like an acceptable compromise. Andy ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
