Am 16.10.2013 10:40, schrieb Dominique Devienne:
If I somehow missed a better work-around to this lack of array-binding, I'm also interested of course, but obviously I'd prefer real array binding.
Maybe I'm missing something - but if I'd have a lot of "InApp- MemAllocations" in the form of different kinds (or "types") of lists, constantly changing their content as well as their listcount - but not their "type" - then I'd use a simple set of userdefined functions (not sure though, how "trigger-happy" those are with regards to your hooking-worries, when you add them into the engine - but this needs to happen only once, at startup). So, after those functions are in place - where's the problem with: select * from table where InMySmallUnsortedArrayExists(some_column) select * from table where InMyLargerSortedArrayExists(some_column) select * from table where InMyHashListExists(some_column) ... etc. for trees or whatever you want to use to speed-up the exists-check. Or more generically with an additional Param: select * from table where InList(@ListTypeEnmValue, some_column) Olaf _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
