Closed GoogleCodeExporter closed 9 years ago
I think it will be better to add per-application logic directly to `index`
command instead of introduce another one.
Second, there is the "index space" concept and may be this task can be done
with per-space logic. Your ideas?
Original comment by daevaorn
on 23 Sep 2010 at 2:28
I'm OK with extending `index` command instead of adding a new one.
As for index spaces, as a generic Django user I used to think in terms of
applications and models, so I do think it's worth following the standard Django
commands way of working "widespread for the site" and "for given applications".
We could extend the `index` command to manage spaces with `--space` option if
that will be required sometime. I wouldn't do it right now though.
Does it make sense for you?
Original comment by esizi...@gmail.com
on 24 Sep 2010 at 7:19
In r367 the `index` command has been extended to support per-application index
update/rebuild.
Original comment by esizi...@gmail.com
on 12 Oct 2010 at 12:19
Original comment by daevaorn
on 12 Oct 2010 at 10:25
Original issue reported on code.google.com by
esizi...@gmail.com
on 23 Sep 2010 at 12:47