On Thu, Apr 16, 2009 at 1:56 PM, Dan McGee <[email protected]> wrote: > On Thu, Apr 16, 2009 at 11:37 AM, Aaron Griffin <[email protected]> > wrote: >> On Thu, Apr 16, 2009 at 11:30 AM, Loui Chang <[email protected]> wrote: >>> On Wed, Apr 15, 2009 at 06:34:28PM -0500, Dan McGee wrote: >>>> Loui- I noticed you applied the patch I sent a day or two after this >>>> one but didn't do anything with this one and its pair (explicit join >>>> usage in query). Just wanted to make sure it didn't get lost. >>> >>> Yeah. I definitely still have my eye on this. >>> Actually I was wondering how to add these indexes to an existing DB, >>> but I haven't had the chance to look into it. >> >> Just running the CREATE statements should work fine, as Dan said they >> do not exist already. >> >> If they did exist, that's another story :) > > Yep, just run the CREATE statement. As I told you over IM, I added > these indexes on the production DB already so that isn't an issue, but > you can of course create them locally. > > If an index with that name already exists, it is just a "DROP INDEX > <name>;" away from not being a problem.
Way off topic... some DBs support "CREATE OR REPLACE ...", which is nice for cases like this.
