[openstreetmap/openstreetmap-website] Give the changesets_count in changeset metadata (#2224)

[Andy Allan]

> nb: changeset metadata call is currently in CGImap land (e.g. https://api.openstreetmap.org/api/0.6/changeset/12). If there's some consensus here, can you please also open up an issue in the cgimap repo?
> 
> What about changeset replication on https://planet.openstreetmap.org/replication/changesets?

Yep, when we nail down the details here, we'll roll it out to the other things that read directly from the database (like cgimap and replication).

> We already have a secondary index on fields user_id and created_at for the changesets table.

I'm not sure why your example used the `changesets_created_at_idx` instead of the `changesets_user_id_created_at_idx`? Maybe it's just postgres not caring because there's not enough data in that db?

A challenge will be figuring out a nice way to make this available in the rails models as an attribute for the changeset.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/2224#issuecomment-492130535
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190514/7d47ef91/attachment.html>