520597 - last_modified column for personas

Status: RESOLVED FIXED

(Mozilla Labs Graveyard :: Personas Plus, defect)

Description

[Jeff Balogh (:jbalogh)]

When AMO starts importing personas, we'll have to compare all the strings in each Persona between the AMO and personas databases to make sure they're in sync.

I'd rather not check all 60,000 personas every time, so a last_modified column would be super helpful for ensuring we only do useful work.

We're going into code freeze on 10/13.  Thanks!

Comment 1

[Toby Elliott [:telliott]]

Can you do it out of the log table? We log every approval, edit approval and delete, which are the three triggers you care about.

Comment 2

[Jeff Balogh (:jbalogh)]

That could probably work.  What would the query look like to get all the persona ids that were updated since yesterday?

Comment 3

[Toby Elliott [:telliott]]

 select distinct(id) from log where (action = 'EditApproved' or action = 'Approved' or action = 'Pulled') and date > date_sub(NOW(), interval 1 day);

Comment 4

[Jeff Balogh (:jbalogh)]

Thanks!  Pulled means that I should remove AMO's copy of the persona, right?

Comment 5

[Toby Elliott [:telliott]]

Yes. If it goes back in, it'll have a followup "Approved"