In some contexts (for example when using RubyCas, which dynamically defines an ActiveRecord model upon self.included?) a call to subclass.respond_to?(:table_exists?) will fail as the still initializing subclass will not have a name to resolve to, which leads to a SQL call like
SELECT '' FROM ''.
Checking the presence of the name will prevent this type of error, by skipping the attribute normalizer entirely.
Prevent still initializing subclasses from going nuts.