Re: EOQualifier proper fetch across to-many?
Re: EOQualifier proper fetch across to-many?
- Subject: Re: EOQualifier proper fetch across to-many?
- From: Lachlan Deck <email@hidden>
- Date: Wed, 07 Mar 2012 05:47:38 +1100
On 07/03/2012, at 4:57 AM, Jesse Tayler wrote:
> why would I have to dump my data just to create the indexes?
Don't.
> should I not be able to create indexes on the fly on mysql?
Yes. Add it to a migration (but verify it won't take forever).
> and yes, this is my first mysql setup and no, I did NOT realize fully that I had to create indexes - some have been, other not, it seems...
>
> anyone have a nice - simple WO-person's explanation of indexing strategy? especially needs for things like a data dump/restore or these attributed correlations spanning multiple entities and supporting/troubleshooting queries?
Other than foreign key indexes, add indexes as needed after profiling your queries (which, as Kieren mentioned, is distinct from foreign key constraints == incompatible at this time with deferred constraints).
Lachlan Deck
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden