Rename column_names to columnNames
Remove license language
Eliminate SqlQueryPackage

SqlQueryPackage has been eliminated in favor of the metadata trait and
folding sql statements into SqlRelation
Eliminate ColumnNameGenerator

Handling of column names is being moved into the appropriate tables.
This change was made because it is really each individual table's
implementation that dictates how column names should be generated. For
example: SQL requires a delicate dance with an RDBMS. But a simple text
file might need auto-generated names because it lacks even basic
headers. Rather than trying to formalize this, each implementation must
simply adhere to the Metadata trait.
Eliminate column name generator
Fold SqlIterator functionality into SqlRelation

SqlRelation can be greatly simplified now that it is itself an
Iterator. By folding the mechanics of iterating over JDBC result sets
into SqlRelation, we gain much better control for when we implement
things like filters or more automated ResultSet handling. Readability
is greatly enhanced by putting all the JDBC ResultSet iteration and
management in one place.
Rename column_names to columnNames and update SimpleDataTable constructor
Import more items from the dataModels package by default
Eliminate SqlQueryPackage

Functionality in SqlQueryPackage has now been separated into the
SqlMetadata trait as well as SqlRelation. As mentioned in other
commits, the primary driver for this is the need to centralize the
iteration over JDBC ResultSets and also to try as hard as humanly
possible not to execute multiple simultaneous database queries. All
metadata from the Metadata trait is marked as lazy to ensure that
nothing is executed until the last possible moment. This also
eliminates some duplicated state and metadata held in the SqlIterator
and query packages.
Reformat if/else statement
Future idea for a SqlQuery object

It may be convenient to have a robust SQL Query object that can be
passed aroud to things like constructors for SqlRelation or DataTable.
This is being added commented out as a placeholder.
Remove SQLRelationColumn

The planned move to make transformations a core part of the API makes
SqlRelationColumn unecessary. A column of data from a SQL relation is
no different than a simple transform that throws out all the columns
but one. Single columns of data, while convenient are largely a nice to
have, not a major feature that rises to the level of needing support
from a specific object.
Remove license
change from column_names to columnNames
Finish rename of column_names to columnNames
Add limited support for transfomed sql tables

In order to simplify the ETL process and avoid the end-user from having
to manage lots of state inside ETL scripts, there is now a
SqlTransform. The SqlTransform wraps another DataTable and applies a
function which transforms the rows of the table. The result is a new
DataTable which may columns that differ in number and type from the
source table.
Add documentation
Update doc
Doc update
Remove reference to .head in test description.

Test was already corrected to use .next