add "custom column" capability to simple_crud call
ability to put in raw sql instead of a column name
default of transforms to sub { return shift; }
use of custom_columns in example app
addition of custom_columns to POD
addition of Michael South to people table in test.sqlite database
Update example/README.pod

Dancer::SimpleCRUD --> Dancer::Plugin::SimpleCRUD
Merge pull request #22 from yaskevich/patch-1

Update example/README.pod
Include use of a hook in example.
Set charset UTF-8
Add a hook which receives row to be added/edited.

New add_edit_row hook which receives a hashref representing the row about to be
inserted/updated, so that it can do various interesting things with it.

Idea from Rene on IRC - cheers!
Brief documentation on hooks
Update Changes
Update README (via pod2readme)
Bump version, preparing to release
Merge branch 'master' of github.com:bigpresh/Dancer-Plugin-SimpleCRUD
Tell Travis CI this is a Perl project.

It has *much* more chance of actually passing tests if run with perl, rather
than ruby.
Have Travis install all prereqs automatically

I don't like the idea of having to list them separately for Travis, so hopefully
this will cause prereqs as defined in Makefile.PL to be installed before testing
begins.
make installdeps doesn't exist.

No such rule in the makefile generated.  However, it seems Travis CI is smart
enough to use `cpanm --quiet --installdeps --notest .` itself if you don't tell
it to do anything else, so let it just do it the sane way.
Work correctly with DB handles other than the default.

Reported by Rahul Kotamaraju in RT #73620.  Sorry Rahul that I didn't notice
that RT ticket for so long!
More changes to use non-default DB connection properly.

As reported by Rahul Kotamaraju in RT #73620, using named connections via
L<Dancer::Plugin::Database>, rather than the default connection, didn't work
correctly, as the desired connection name wasn't always supplied to the
`database()` keyword.
Handle Dancer prefix setting changing later.

As reported by Rahul Kotamaraju in RT #73620, if the Dancer `prefix` setting
changes after `simple_crud()` is called, some parts (e.g. the routes defined)
will have used the prefix setting as it was when `simple_crud` was called, and
other parts (e.g. working out URLs to redirect to after editing, or for add/edit
links etc) will use whatever the Dancer prefix setting is at that time - which
could well have been changed by subsequent code.

Rememeber the value as it was when `simple_crud` was called, and use that value
later.
Bump version
Update Changes