Record Filtering Using "OR" Condition

I only imagine a workaround, sorry

TBMyTable.SETRANGE(ColumnA, 'xxx');
if TBMyTable.findfirst then begin
  repeat
    TBMyTrueTable.get(TBMyTable.primarykey);
    TBMyTrueTable.mark(true);
  until TBMyTable.NEXT = 0;
end;

TBMyTable.RESET;
TBMyTable.SETRANGE(ColumnB, 'xxx');
if TBMyTable.findfirst then begin
  repeat
    TBMyTrueTable.get(TBMyTable.primarykey);
    TBMyTrueTable.mark(true);
  until TBMyTable.NEXT = 0;
end;

TBMyTrueTable.markedonly(true);

TBMyTable and TBMyTrueTable are 2 record variables of the same record.

I don't think this code will generate an "OR" statement, but the result will be the one you want.
Obviously this method is slow. Hope someone have something better

I may be butchering DeMorgan's rules, but let me see if I can get this:

we want Column A = 'xxx' OR Columng B = 'xxx' and we can only use ANDs.

so that should be equivalent to NOT ( Column A <> 'xxx' AND Column B <> 'xxx' )

So we can get this:

table.setfilter( A, '<>xxx') ;
table.setfilter( B, '<>xxx') ;

table.findset ;

and we have all the records in the table that are NOT in our filter criteria. Now we have to get that set's complement. There are two ways I see to do that:

1. We can MARK all of these records. Clear the filters. And then toggle the marks on all of them. The remaining marked records are in our intersection of two sets.

2. Get all of table withotu filters into a temporary record. Loop through the 'not' set and delete those records from teh temporary record.

Nice thing about (1) is that you are never looping through records, so for large data sets it should be really fast. (2) avoids using marks, and for most filtering criteria should be faster than Belias method.

That's a good point, perhaps the marking solution is better.


Perhaps the simplest thing of all is to create a new boolean field that is true if either field has the given value.

Not marking with a boolean when you do the call, marking with a boolean through normal transactions. That is to say putting code in the onvalidate triggers of the fields. You are sort of doing some preprocessing for the query.

Also perhaps both solutions could be combined. -- marking a temporary record instead of the database.

Of course the temp table would need to be populated in the first place -- and but we have do that in either scenario.

There is a thread about new features.
http://www.mibuso.com/forum/viewtopic.php?t=22245

I've asked for something something like this.

Table.setrange(Field1,'value1') OR
Table.setrange(Field1,'value1') ;