Preserve info['bind_key'] when creating table

- When creating a table on in the non-declarative way, info/bind_key was lost
Fixed some broken logic.  This fixes #57
Typo fix: 'may items' => 'many items'
Link to the shell's "Request Context" section.

The "Diving into context locals" section has moved elsewhere in the
Flask documentation (to the 'reqcontext' chapter), so link to the most
appropriate section of the 'shell' chapter instead.
Merge pull request #56 from ThiefMaster/patch-1

Preserve info['bind_key'] when creating table
Changed image mode from 755 to 644.
Update docs/queries.rst
Switched to new naming scheme and added support for Flask 0.9 specifics.
New config.cfg
Updated changelog
Updated docs
fixed typo in docs/quickstart.rst
Merge pull request #87 from coryalder/patch-1

fixed typo in docs/quickstart.rst
apply_driver_hacks will now consider all types of mysql drivers, e.g., oursql, not just the default driver, when deciding whether to apply mysql hacks. Fixes #48 and improves upon original issue #2.
When counting the total number of results, remove the "ORDER BY" clause if present.
Record operations only for signalling sessions.

In some scenarios model classes derived from SQLAlchemy(...).Model
may be used with basic SQLAlchemy session instances which aren't
extended with signalling functionality.

Before this fix, when you try using a vanilla session with
such models, you would get exception like this:

  File ".../flask_sqlalchemy.py", line 163, in after_insert
    return self._record(mapper, instance, 'insert')
  File ".../flask_sqlalchemy.py", line 172, in _record
    s._model_changes[pk] = (model, operation)
AttributeError: 'SessionMaker' object has no attribute '_model_changes'

With this fix, this problem is resolved.
commit on app/request context teardown
increase indentation
document the SQLALCHEMY_COMMIT_ON_TEARDOWN flag
Merge pull request #115 from mgax/commit-on-teardown

Commit on teardown