Yet I don't want to do this reversal "in my application". I am not a C programmer and would have to rely upon data-providers to talk to the database. Providers, as good as they may be, are not 100% transparent conduits between the client app and the database. Right now, three of them are returning different query plans from what SQLite3.exe returns, for example. In respect to the flip() function, what if a provider should add a bit of "intelligence" and throw a malformed Unicode character exception when it sees a composed Unicode character that makes no sense because its raw codepoints have been reversed?
I don't know if that hypothetical scenario is far-fetched; but it's not far-fetched to ask for a function like this because the mainstream databases all provide the ability to reverse the raw codepoints of a text string along with their other string-handling functions. Such a function is common, not unusual. Not that SQLite needs to do everything the other databases do. You do have demands to remain "Lite". But I don't believe that a raw reverse-string function adds much "weight". A UnicodeIntelligentReverse() that preserves combined Unicode forms during the reversal could be weighty but the raw-flip is a tiny bit of code. Regards Tim Romano Igor Tandetnik wrote: > Tim Romano <tim.rom...@yahoo.com> wrote: > >> I respectfully disagree, Roger, about the simplicity. Creating an >> external DLL would complicate my distribution scenario significantly >> because I'll have just as many users of my little database >> application working with Apple OSX as with Windows. >> > > You don't need external DLL. You can implement your custom function directly > in your application. > > Igor Tandetnik > > _______________________________________________ > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
