You are not doing yourself any favors by changing the topic without changing the subject and removing the non-applicable messages.
Because I had been following this thread, I read your new comments, but anyone who might be able to help with Solid will skip the message. What's worse, I've been answering based on the assumption that the thread involved Oracle. It appears that has not been true since you chipped in. -- Mac :}) ** I normally forward private questions to the appropriate mail list. ** Ask Smarter: http://www.tuxedo.org/~esr/faqs/smart-questions.htm Give a hobbit a fish and he eats fish for a day. Give a hobbit a ring and he eats fish for an age. ----- Original Message ----- From: "BAO RuiXian" <[EMAIL PROTECTED]> To: "Michael A Chase" <[EMAIL PROTECTED]> Cc: "ariel mastracchio" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, February 07, 2002 02:50 Subject: Re: Problems DBI/DBD::Oracle/Perl.. > . . . > I use Solid version 2.2, not sure about Oracle though. > > BTW, I have another issue concerning DBI need to consult your gurus. According > to the experts from the Solid company, for a statement if there are less than 10 > values inside IN() in the WHERE clause, the solid version 2.2 engine will do > unions by each value, and this will take about 3 minutes for one of my SQL > statement when I run it from the Solid Editor. But, once there are more than 10 > values inside IN(), for the same statement also running from the Solid editor it > would take forever, because the solid engine in this case will scan the whole > tables. The experts from the solid company told me I can change the default > value by running the statement > > SET SQL CONVERTORTOUNIONS YES COUNT 100 > > After I ran the above SQL statement via the Solid Editor to the database, my own > SQL statement with 21 values inside IN() only takes 6 minutes. But, the problem > is it still takes about one hour if I run my statement via DBI Perl application. > So, my question is, why there is a so big difference in time between the Solid > Editor and the DBI application? Or DBI has its own strategy to optimize query > plan? I noticed after the default value changed to 100, my DBI application runs > better (1 hour) than before (endless). > > Any input from your gurus are highly appreciated.
