network profile
| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 11 months |
| seen | Jul 6 '12 at 14:10 | |
| stats | profile views | 3 |
|
May 30 |
comment |
MySQL using a index referencing a different column Change #2: id is the primary key, shouldn't the optimizer do an index_merge to do the same? |
|
May 30 |
comment |
MySQL using a index referencing a different column Change #1: This is something I will try. |
|
May 30 |
comment |
MySQL using a index referencing a different column Sadly this isn't possible. The versioning system in the application is (ab)used. In some of the tables the history records are used for tracking if a customer has spend a credit on action. So that the customer doesn't have to spend another credit for the same action. IMHO this is not supposed to be done by using the versioning system. But it is there and at the moment I am not in the position to change this. |
|
May 29 |
awarded | Student |
|
May 29 |
comment |
MySQL using a index referencing a different column @ypercube you are a genius ( or I am a idiot ). We have an creationdate, startdate and enddate. The enddate is always null for a parent record. Which makes it perfect indexable :) |
|
May 29 |
awarded | Editor |
|
May 29 |
revised |
MySQL using a index referencing a different column added 141 characters in body |
|
May 29 |
comment |
MySQL using a index referencing a different column No. If we just keep the records for auditing purpose then you would be right. But the versioning is used (abused) in our business application. I am not allowed to change the business application at this time. |
|
May 29 |
asked | MySQL using a index referencing a different column |
