But yes, these are, in retrospect, so "obvious".
Can we merge them into the core?
http://is.gd/a2J9
Sean
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.o
Sean Cribbs said the following on 12/03/2008 09:46 AM:
> I've applied Yevgeny's indexes (without the uniqueness constraints -
> YAGNI) and here's some circumstantial (i.e. not rigorous) results from
> running the spec suite:
> BEFORE
...
> ---
> real 137.84
> user 58.80
> sys
I've applied Yevgeny's indexes (without the uniqueness constraints -
YAGNI) and here's some circumstantial (i.e. not rigorous) results from
running the spec suite:
BEFORE
Integration: 4.263972
Models: 51.04876
Controllers: 25.428781
Helpers: 1.062501
Lib: 2.16
Sean Cribbs said the following on 12/01/2008 07:34 PM:
> I agree on most of those, however, I disagree about using unique
> indexes. Uniqueness is already specified in the application layer and
> unique indexes (in my experience) create more problems than they solve.
It depends on how you look
Yevgeny Smirnov said the following on 12/01/2008 04:25 PM:
> I think, it's good to create the following DB indexes:
>
> add_index "pages", ["class_name"]
> add_index "pages", ["parent_id"]
> add_index "pages", ["slug", "parent_id"], :unique => true
> add_index "pages", ["virtual",
I agree on most of those, however, I disagree about using unique
indexes. Uniqueness is already specified in the application layer and
unique indexes (in my experience) create more problems than they solve.
Sean
Yevgeny Smirnov wrote:
I think, it's good to create the following DB indexes:
I think, it's good to create the following DB indexes:
add_index "pages", ["class_name"]
add_index "pages", ["parent_id"]
add_index "pages", ["slug", "parent_id"], :unique => true
add_index "pages", ["virtual", "status_id"]
add_index "page_parts", ["page_id", "name"], :unique
