Opened 13 years ago

Last modified 13 years ago

#65 closed defect (FIXED)

Handle indexes ourselves instead of via mongokit

Reported by: Christopher Allan Webber Owned by: Christopher Allan Webber
Priority: minor Milestone: 0.0.3
Component: programming Keywords:
Cc: Parent Tickets:


`\_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.

Change History (3)

comment:1 by Christopher Allan Webber, 13 years ago

Alternately 0.7.0 could come out and solve this for us ;)

I think it's fine for tickets to not block on this and use the
index feature of mongokit until we figure this out though.

comment:2 by Christopher Allan Webber, 13 years ago

Component: Programming
Milestone: 0.0.3
Owner: set to Christopher Webber
Status: NewClosed
Horray! I did this and merged it into master and pushed that code.
See the mediagoblin/db/ for more information, but
basically if you run ./bin/gmg migrate it should update the indexes
for you also.

comment:3 by Will Kahn-Greene, 12 years ago

The original url for this bug was .

Note: See TracTickets for help on using tickets.