2010/5/13 Platonides <[email protected]>: > That doesn't match the expected behavior from the SQL file. > Are you sure it works like that? Since there's a primary key on > (cr_repo_id, cr_id), you can't have multiple entries [on the same > repo] with the same cr_id. cr_path contains the shortest common parent > for all the involved files. > Thus, a change to /trunk/phase3 will store only /trunk if it also > applies to a branch. Or / (or is it ''?) if it also changed something at > the repository root, which is really unlikely. > You're right, my apologies. That query was meant to run on the code_paths table instead:
SELECT COUNT(DISTINCT cr_id) FROM code_paths, code_rev WHERE cr_repo_id=cp_repo_id AND cr_id = cp_rev_id AND cp_repo_id=1 AND cr_timestamp >= '$epoch' $extra AND cp_path = '/trunk/phase3' Could probably drop the DISTINCT as well, but it's early morning as I write this so I'm not sure. Roan Kattouw (Catrope) _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
