Hi,

i'm working in an enterprise that have Baan IV B40c.66. i'm new here and i'm learning with the old method of "trial and error".

i think i understand (10 months and a million cups of coffee after i started) some of the issues for baan performance (at least those that refer to using indexes, avoid some joins in some cases where is better to do the new select in the selectdo part...

Now my question is because i see in programs a lot of inrange's and (field1 > value_min and field1 < value_max) (for this one i'm prefer between because is more legible) and (field1 <> value and field1 <> value and field1 <> value)... i'm guessing that using between and (in or not in) is not standard in BaaN programs are these constructs low performance? or are there other reasons?

btw, we are using BaaN IV B40c.66 with informix 9.21 TC7 (driver level 1) running at Windows NT

regards,
Jaime Casanova

The difference with 'between' and 'inrange' comes when you are comparing an index with multiple parts (or other combined fields).

Inrange will compare the range for each field in the combined index individually, and Between will apply the range to the combined field all together.

See the WIKI link for further explanation and examples:

http://www.baanboard.com/programmers_manual_baanerp_help_functions_database_handling_sql_and_combined_fields

As you are using Level 1, you have to keep in mind that not all solutions for you mentioned on this board will help you. Therefore: keep on tracing check out the performance on the queries and find the logic why things are going slow. Feel free to use the documents on this SIG and forum to improve your knowledge on this topic.

I know this is a general answer, but in general this problem is very broad. More specific to your question: there is no specific performance reason for using IN RANGE or BETWEEN, it is more a developer decision.

Hope this helps,
Dick

Now my question is because i see in programs a lot of inrange's and (field1 > value_min and field1 < value_max) (for this one i'm prefer between because is more legible) and (field1 <> value and field1 <> value and field1 <> value)... i'm guessing that using between and (in or not in) is not standard in BaaN programs are these constructs low performance? or are there other reasons?


thanks to all who answered me...

but part of my question is still unanswered, what about in and not in... its better to use them or use ORed/ANDed constructions to see if a field does/doesn't contain some list of values?

Thanks in advance,
Jaime Casanova

The usage of an IN/NOT IN should result in the same data approach as an AND/OR. As the writing of an IN/NOT IN is sometimes easier to show the logic of a query, I mostly prefer this one.

So, for performance it should not matter. Maybe there are exceptions, but I don't know them yet.

Hope this helps,
Dick