Settings build unnecessary in schemaupdate/schemavalidate
Description
the fix for causes a new Settings object to be built for each table mapping when doing a schema update or validate. this is unnecessary.
in some scenarios, it might be expensive to build a new settings object because it communicates with the database for metadata and it also creates a cache provider, which might be expensive to create for clustered caches.
to fix, buildSettings (lines 947 and 1069) should be pulled out of the while loop.
the fix for causes a new Settings object to be built for each table mapping when doing a schema update or validate. this is unnecessary.
in some scenarios, it might be expensive to build a new settings object because it communicates with the database for metadata and it also creates a cache provider, which might be expensive to create for clustered caches.
to fix, buildSettings (lines 947 and 1069) should be pulled out of the while loop.