first of all no you cannot do it like you mentioned because RedBean requires each table to have a column named id (lowerCase) being auto-increment and primary key. Take a look at the schema documentation.
Next even if it would work, I wouldn't recommend doing so because you're violating DB normalization principles by including the revision in the same table. Most of the time you just need the latest revision but keeping all of them inside the same table just bloats your queries. So instead I'd advice to maybe try a solution like described in my Redbean ReBean module. It uses separate tables for revisions plus automated creation via triggers.