Account for schemas in loadTables
Right now we're just dropping things from
public right on to the massive instance which works for many situations. I think it would be better to account for schemas as well - as that's a good approach for keeping your DB uncluttered when it gets to be rather large.
There are several reasons why one might want to use schemas:
- To allow many users to use one database without interfering with each other.
- To organize database objects into logical groups to make them more manageable.
- Third-party applications can be put into separate schemas so they do not collide with the names of other objects.
Schemas are analogous to directories at the operating system level, except that schemas cannot be nested.
Our current tableSql pulls the schema (I think) so we have access to it. If the schema is
public I say we do what we've been doing (pop it onto the massive instance). If it's not, namespace thus: