"D. Richard Hipp" <[EMAIL PROTECTED]> writes: > As an interim workaround, you could defined your own > "like()" function using the sqlite_create_function() API > that implemented built-in escapes. Any user-defined > function named "like()" is used to implement the LIKE > keyword of SQL.
That seems pretty dangerous, since no one would expect that function name to exist as a public symbol in a library. I would suggest changing the name of the internal like() function to sqlite_like() or some equivalent, to avoid potential problems. Being able to overload internal functions could be a nice feature (which should be documented) but it seems the names should be clearly associated with sqlite. Thoughts? Derrell --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
