> Adding entire tables just doesn't seem worth it for this use case alone. If you peek at a particular table often enough and it has a crazy enough enum to may

> Adding entire tables just doesn't seem worth it for this use case alone. If you peek at a particular table often enough and it has a crazy enough enum to maybe justify making your life a little easier, what you can do is add a table just for debug purposes and use a view that maps the int to it, but otherwise only use the direct int:enum cast in your app/orm/etc. thereby not paying any runtime cost for foreign keys or integrity checking.