Use tuple batch buffer in profiling logger because we benefit from faster writing (i.e. copy for postgres). Fixes #670
Merge remote-tracking branch 'origin/master' into profiling-faster-insert

Conflicts:
	src/edu/washington/escience/myria/profiling/ProfilingLogger.java
Rename constants for profiling schemas/relations. Rewrite writing of resource records.
Remove schema parameter from accessMethod.tupleBatchInsert because the tupleBatch has a schema
Delete unused sqlite util methods
Remove unused param
instead of running a query, just add the data to the catalog in importDataset
Revert "instead of running a query, just add the data to the catalog in importDataset"

This reverts commit 7b6a6edd2b28e359d44bd9f2d2c747abb8b7ce0e.
Add profiling relations to catalog without actually running a query. Fixes #647
DbInsert: schema during insert

Also improve some error messages.
ConnectedComponentTest: fix schema error

We were using the wrong column names
UnionAllTest: differing column names in children
UnionAll: repair output column names if necessary

Also clean up some error messages.
Schema: test compatible
UnionAll: verify error thrown with incompatible children
Merge branch 'master' into profiling-faster-insert
Merge pull request #672 from uwescience/profiling-faster-insert

Use tuple batch buffer in profiling logger