One interim solution would be to provide your own custom revision entity implementation so that you can specifically assign the column names to the various REVINFO attributes that you'd like to use for consistency in your database schema. The behavior you experience only occurs when using the default revision entity implementations as the column names are static and don't change based on user customizations.