could check if the cover art is already in CAA maybe?
2015-10-31 30410, 2015
Freso
/query Leftmost
2015-10-31 30412, 2015
Freso
...
2015-10-31 30454, 2015
chirlu`
SELECT extract_path_value(edit.data, 'link_type/id') AS rt, link_type.link_phrase, edit.status, COUNT(*) FROM edit, link_type WHERE edit.type = 90 AND extract_path_value(edit.data, 'link_type/id')::int = link_type.id AND edit.id BETWEEN 33000000 AND 34000000 GROUP BY rt, link_type.link_phrase, edit.status;
2015-10-31 30408, 2015
chirlu`
bitmap ^ (untested, but compiles)
2015-10-31 30433, 2015
regagain joined the channel
2015-10-31 30448, 2015
chirlu`
bitmap, new attempt with a CTE and a smaller sample: WITH foo AS (SELECT extract_path_value(edit.data, 'link_type/id')::int AS rt, edit.status FROM edit WHERE edit.type = 90 AND edit.id BETWEEN 33900000 AND 34000000) SELECT foo.rt, link_type.link_phrase, foo.status, COUNT(*) FROM foo, link_type WHERE foo.rt = link_type.id GROUP BY foo.rt, link_type.link_phrase, foo.status ORDER BY COUNT(*) DESC;
So, in summary: 31756 edits were applied, 17 were voted down, 108 got cancelled.
2015-10-31 30444, 2015
chirlu`
2 failed for technical reasons.
2015-10-31 30425, 2015
chirlu`
Thats 0.05% of the add-relationship edits voted down, 0.34% cancelled.
2015-10-31 30449, 2015
chirlu`
0.006% failed.
2015-10-31 30454, 2015
chirlu`
bitmap, without autoedits and a larger sample: WITH foo AS (SELECT extract_path_value(edit.data, 'link_type/id')::int AS rt, edit.status FROM edit WHERE edit.type = 90 AND edit.autoedit = 1 AND edit.id BETWEEN 33000000 AND 34000000) SELECT foo.rt, link_type.link_phrase, foo.status, COUNT(*) FROM foo, link_type WHERE foo.rt = link_type.id GROUP BY foo.rt, link_type.link_phrase, foo.status ORDER BY link_type.link_phrase, COUNT(*) DE
Why not store DB-specific info in a table in individual projects, with editor ID (from MeB) as the key?
2015-10-31 30446, 2015
LordSputnik
Then when the user logs in via MeB, we somehow get the user ID, and the specific site gets the specific info?
2015-10-31 30405, 2015
chirlu`
LordSputnik: But how are the specific sites notified about removals? The user will never log in again.
2015-10-31 30406, 2015
Gentlecat
does that mean that we actually don't have to use oauth2 internally?
2015-10-31 30454, 2015
Gentlecat
chirlu`: can check the same table
2015-10-31 30410, 2015
chirlu`
Gentlecat: What table?
2015-10-31 30447, 2015
Gentlecat
user table in MeB database
2015-10-31 30458, 2015
Gentlecat
maybe LordSputnik meant something else
2015-10-31 30401, 2015
LordSputnik
OAuth could be avoided internally if you can access the MeB user table directly in all internal projects
2015-10-31 30436, 2015
LordSputnik
But I think we might as well stick with OAuth
2015-10-31 30414, 2015
LordSputnik
The benefit of storing site-specific data with the sites is that it's potentially less work to implement that than a way of storing and accessing that data on MeB
2015-10-31 30409, 2015
alastairp
LordSputnik: we basically do already
2015-10-31 30449, 2015
LordSputnik has quit
2015-10-31 30401, 2015
Freso
Other people are more than welcome to assist in adding to the notes too. Just let me know your Google id thingies.
