On second thought, I think it makes more sense to give the DAO a parameter that specifies all the fields to select. If not specified, it fetches `*`. That way you have a logical way to ensure a `*` select for things like creating a new revision from a previous one, which is super important.

Then the column listing inside of `getMultipleRevisions` comes out of the DAO into the content API for `ContentAPI.getRevisions`.

Also, in `oae-content/lib/search.js`, it actually only seems to need the `etherpadHtml` from the revision, so that can be changed to fetch **only** the etherpadHtml from the DAO.