Added schema for collections and collection_works tables.
Updated result classes for collection and collection_works tables.

Added new result classes Collection and CollectionWork, for the new tables
collections and collection_works, respectively.  There is now also a one-to-
many relationship between the users and collections table, resulting in a new
has_many relationship in the User result class; and there is a new many-to-
many relationship between works and collections, where collection_works is the
linking table.
Added primary key to CollectionWork result class.
Added primary key to collection_works table.
Added many-to-many relationship between collections and works.

The DBIx::Class::Schema::Loader module (as of version 0.07015) only
automatically creates many-to-many relationships if the linking tables for
those relationships are comprised only of the foreign keys relating the two
tables in the relationships.  The collection_works table has additional
metadata fields (added_timestamp and notes), so the many-to-many relationship
must be defined manually.  Also, we want the metadata values included in the
result sets for the linked objects, so the relationship would need to be
redefined, anyway.
Added initial version of WorkToRead schema class.
Added missing columns to the view's select clause.

The initial version of this view only returned a few columns, specifically the
columns used while testing the query.  This query should return all (or, at
least, most) of the columns from the works table, as well as some columsn from
the work_references table.  The select statements inside the CTE and the outer
select statement have been updated to return these values.
Added metadata for the work_reference columns used in the view.
Re-added the relationships from the Work result set.

This view, WorkToRead, has at least all of the columns from the works table,
so it is possible it will make use of all of its relationships.  Added to this
view each of the relationships in the Work result set.  However, corresponding
relationships have not been added to the related result sets, so they would
need to be added later if the reciprocal relationships are needed.
Removed "is_foreign_key" from the referenced_work_id metadata.
Reversed referenced_work_id and referencing_work_id columns.

The initial version of this query recursively fetched all works that
referenced the indicated work.  This is the opposite of what we want: all
works that are referenced by the indicated work.  Thus, all columns relating
to these two columns had to be swapped to get the desired output.
Added column information for work_references columns.

The metadata about the work_referneces columns (referencing_work_id and depth)
were actually only comments about these columns; ResultSet objects created
from this view did not actually have these columns.  Now, actual metadata for
these columns have been added, so they are actually fetched now.
Include columns from user_work_data in view's columns.

Added the read_timestamp, understood_rating, and approval_rating columns from
the user_work_data table in the select clause in the query, the columns
comments, and the list of columns for the view.
Added ResultSet view for getting all works in a work's connected component.
Added view to return all works with user data and references.

Added view ViewWorksWithUserData.  This view returns a list of all works, along
with a specific user's data for each work (or null, if no user is specified).
Each work also has all works that reference it, so a work referenced multiple
times will be returned multiple times.

This view is used instead of simply using the Work result set's
user_work_datas relationship, as that will return no rows for a work if the
indicated user does not have any metadata for that work (no record in
user_work_data), but at least one other user does have metadata for that work.
Advanced version to 0.006.
Added version info for 0.006.