This week's book giveaways are in the Scala and Android forums. We're giving away four copies each of Machine Learning Systems: Designs that scale and Xamarin in Action: Creating native cross-platform mobile apps and have the authors on-line! See this thread and this one for details.
The optimiser would have to generate a new query plan for each table. One reason for this is that different tables may have different indexes so the method of accessing the data may be different. Even if the indexes, etc. were all the same on different tables, the optimised query plan only provides a template for substitution of values.
The same query using different values can be executed the same way. The same query using a different table must be executed differently (i.e. on a different table! )
posted 13 years ago
Hi Julian, Thanks for the reply. I also had a feeling that it varies from table to table, but just wanted to confirm it. Thanks for the details .
I am a man of mystery. Mostly because of this tiny ad: