remove oid check from rasql generated by petascope

[Dimitar Misev]

All rasql queries generated by petascope have a WHERE clause like this:

WHERE oid(<coverage>) = <oid>

This is unnecessary as every coverage corresponds to a collection with a single object in it as far as I know. The WHERE clause should be removed to reduce clutter in the queries.

[Vlad Merticariu]

Having a single object per collection is a convention, but is not enforced. I don't see it as clutter, just a safety mechanism.

[Dimitar Misev]

It is enforced in petascope, so there's no problem as long as you don't fiddle with the coverage-collection directly in rasql.

It's annoying mostly because the rasql queries from the logs are not portable as is, requiring to always remove this WHERE clause before sharing.

[Vlad Merticariu]

Ok, makes sense for portability. We just need to make sure in InsertCoverage that the collection is empty (and I believe you're right that we do, in that a new collection is automatically created if something with the same name already exists).