I would have to look into the details of what QueryDefault is doing, but in the QueryByPattern, any property that is "null" is automatically wildcarded. I'm not sure how the provided strings map onto fields and values.
When I've needed to "combine" WHERE clauses, I've used multiple QueryByPattern calls and merged the results. On 27 Aug 2013 at 18:52, Jeremy Gurr wrote: > I did check those out, but the limitation is that they are based on > prepared statements that have a fixed where clause. I need to be able > to construct an arbitrary list of fields that are included in the > where clause only if the value associated with them is not null. Is > there a way to do this with the pre made queries referred to by > QueryDefault? > > Jeremy >
