﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	resolution	keywords	cc	parents
65	Handle indexes ourselves instead of via mongokit	Christopher Allan Webber	Christopher Allan Webber	"{{{
#!rst
See:
`https://groups.google.com/group/mongokit/browse\_thread/thread/50c0c9ab4a313010 <https://groups.google.com/group/mongokit/browse_thread/thread/50c0c9ab4a313010>`_

It looks like the indexes feature in mongokit is acknowledged as
not well implemented for production. We should figure out a nice
way of doing this ourselves, possibly via a command to ./bin/gmg
and then adding / removing indexes later via migrations?

Alternately we could keep some value in the database about whether
indexes have **ever** been set up, and if not, set up the current
indexes, and then handle all subsequent ones via migrations? We
don't want it to be hard to have new users have migrations from the
get-go without having to run an extra command, maybe.



}}}"	defect	closed	minor	0.0.3	programming	FIXED			
