meta user
network profile
| bio | website | code.ghostdev.com |
|---|---|---|
| location | Idaho Falls, ID | |
| age | 29 | |
| visits | member for | 8 months |
| seen | Mar 28 at 17:10 | |
| stats | profile views | 0 |
Programming: An industry where you have to design your own tools before you can use them, and other people can redesign them for you after you've put them into use.
|
Sep 25 |
comment |
Minimizing Indexed Reads with Complex Criteria @ypercube - No, I'm not certain that's where the performance degradation is. That's why my question was "do I need to be concerned with this, or is it normal behavior of an index?". It's something I noticed while monitoring the database, and I considered it unexpected. I would not expect it to continue to scan the preceding rows when I provide a where clause against an indexed column. FWIW, modifying the index to include ticket_id actually performed worse than just having Status indexed. |
|
Sep 25 |
revised |
Minimizing Indexed Reads with Complex Criteria To encompass comments. |
|
Sep 24 |
awarded | Custodian |
|
Sep 24 |
awarded | Editor |
|
Sep 24 |
reviewed | Approve suggested edit on Minimizing Indexed Reads with Complex Criteria |
|
Sep 24 |
revised |
Minimizing Indexed Reads with Complex Criteria Better title. The example code isn't really that complicated. |
|
Sep 24 |
awarded | Student |
|
Sep 24 |
asked | Minimizing Indexed Reads with Complex Criteria |
|
Sep 24 |
awarded | Autobiographer |
