> "...Where SomeColumnContent Like '%someother[*]part%' Thanks Olaf, that works fine. As my customers won't get this I think I might let my code take care of this.
How would it work with glob? RBS On Wed, May 26, 2010 at 7:05 PM, Olaf Schmidt <[email protected]> wrote: > > "Bart Smissaert" <[email protected]> > schrieb im Newsbeitrag > news:[email protected]... > >> Yes, it must be either my code or the wrapper to blame. >> Thanks for confirming. > > It's a wrapper-"problem", but a perhaps a coding problem > as well... ;-) > > The wrapper overrides sqlites internal Like-Function, > to achieve (Unicode-)BSTR mapping. > > Internally VBs normal Like-Function then does "all the rest". > > The wrapper (due to compatibility reasons with regards > to JET *.mdbs) also understands their older "like-syntax": > "...Where SomeColumnContent Like '*somepart*' > (in this regards behaving somewhat similar to SQLites glob, > which BTW was _not_ overriden)... > > But it supports the "default-like-syntax" as well: > "...Where SomeColumnContent Like '%somepart%' > > To specify single chars, which are equal to the "comparison- > descriptors" you have to "escape them" within brackets: > "...Where SomeColumnContent Like '%someother[*]part%' > > If the above should not work, then this would be considered > a "real wrapper-bug". ;-) > > > HTH > > Olaf Schmidt > > > > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
