we tried keeping everything in the same table in some web app of ours. we used a version id and an extra versioning status field that kept track of the states "

we tried keeping everything in the same table in some web app of ours. we used a version id and an extra versioning status field that kept track of the states "latest published", "latest draft", "archived" which kinda worked fine... the disadvantage is bloat, as in our case the history data was rarely used at all and just there as a safeguard.