In a message dated 00-01-26 19:33:34 EST, you write:
In version 4.1.5 there is a limit to the amount of dimension values one can place a query condition on. I believe this limit is 155 values. Does anyone know if this is still the case in version 5?
Interesting… I had never heard of this as a limitation. Just to check, I created a query and was able to create 160 conditions. I got bored at that point and quit, but it appeared that I would have been able to continue…
I am willing to bet that there is not a limit on the number of conditions, but that there is a limit on the size of the SQL that is ultimately generated. I am not aware of any database that would limit the amount of work done in a where clause, but most databases limit the size of a single block of SQL code.
You could check this quite easily. Open your query that has 155 conditions and try to add more result objects. If that is not allowed, then your SQL code has reached the size limit. In other words, you have not reached a limit on conditions, but rather the amount of text that can be generated in the SQL.
If that is the case, then version 5.0 will not improve, as your database engine will be the same.
If this is not the case, I can’t imagine why this limitation would exist.
I’m really curious: what sort of query do you have that requires over 150 conditions? Have you considered making some predefined conditions that might include more complex data logic? Or using a sub-query? Or joining to a lookup table?
I can’t imagine sitting down with a user and telling them they have to create 155 (or more!) conditions to get a correct answer…
Regards,
Dave Rathbun
Integra Solutions
www.islink.com
Listserv Archives (BOB member since 2002-06-25)