| List: | Internals | « Previous MessageNext Message » | |
| From: | Baron Schwartz | Date: | January 3 2008 7:41pm |
| Subject: | Re: what should an assert_efficient_sql check for? | ||
| View as plain text | |||
On Jan 3, 2008 2:21 PM, Phlip <phlip2005@stripped> wrote: > > 10000 < explanation['rows'] ) || > > Curiously, why would a select-all over 1535 records return 1164 rows? > > Is that just because >300 were already buffered in memory? No, it's just that the 'rows' is an estimate based on storage engine statistics, and is wrong. (I'm guessing you're looking at InnoDB tables).
| Thread | ||
|---|---|---|
| • what should an assert_efficient_sql check for? | Phlip | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Jay Pipes | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Phlip | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Phlip | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Baron Schwartz | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Phlip | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Baron Schwartz | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Phlip | 3 Jan |
| • Re: what should an assert_efficient_sql check for? | Phlip | 4 Jan |