forgot authors!!
sqlalchemy/dialects/postgresql/__init__.py:
- Added import references to JSON class

 sqlalchemy/dialects/postgresql/base.py:
 - Added visitor method for JSON class

 sqlalchemy/dialects/postgresql/pgjson (new):
 - JSON class, supports automatic serialization and deserialization of json data, as well as basic json operators.
Merge branch 'rel_0_9' of https://github.com/nathan-rice/sqlalchemy into rel_0_9
Implements TSVECTOR type for postgresql.

Signed-off-by: Noufal Ibrahim <noufal@nibrahim.net.in>
Updates documentation for tsvector type.

Signed-off-by: Noufal Ibrahim <noufal@nibrahim.net.in>
Adds tsvector to ischema_names for reflection to work.

Signed-off-by: Noufal Ibrahim <noufal@nibrahim.net.in>
Adds test to verify tsvector creation.

Signed-off-by: Noufal Ibrahim <noufal@nibrahim.net.in>
sqlany dialect moves to github
Merge branch 'tsvector' of https://bitbucket.org/nibrahim/sqlalchemy/branch/tsvector into tsvector
- round trip test
- changelog
- some doc rearrangement
 sqlalchemy/dialects/postgresql/pgjson:
 - Fixed reference to HSTORE
 - Corrected spelling of SQLAlchemy

 sqlalchemy/dialects/postgresql/psycopg2:
 - Added psycopg2 specific wrapper type for JSON which uses inherent json deserialization facilities
 - Added code to detect and utilize the JSON wrapper if psycopg2 >= 2.5

test/dialect/postgresql/test_types:
- removed reference to use_native_hstore
 sqlalchemy/dialects/postgresql/psycopg2:
 - Removed unneeded import of psycopg2.extensions
 sqlalchemy/dialects/postgresql/pgjson:
 - Added support for additional operators
 - Made return as json default (rather than text)
 sqlalchemy/dialects/postgresql/pgjson:
 - Updated documentation for JSON class
- The :class:`.exc.StatementError` or DBAPI-related subclass
now can accomodate additional information about the "reason" for
the exception; the :class:`.Session` now adds some detail to it
when the exception occurs within an autoflush.  This approach
is taken as opposed to combining :class:`.FlushError` with
a Python 3 style "chained exception" approach so as to maintain
compatibility both with Py2K code as well as code that already
catches ``IntegrityError`` or similar.
- The :class:`.ForeignKey` class more aggressively checks the given
column argument.   If not a string, it checks that the object is
at least a :class:`.ColumnClause`, or an object that resolves to one,
and that the ``.table`` attribute, if present, refers to a
:class:`.TableClause` or subclass, and not something like an
:class:`.Alias`.  Otherwise, a :class:`.ArgumentError` is raised.
[ticket:2883]
- implement "literal binds" for the text() clause, [ticket:2882]
move things that are 90% behavioral improvements to that section.  the list of things
that can definitely people should be more focused.
- Error message when a string arg sent to :func:`.relationship` which
doesn't resolve to a class or mapper has been corrected to work
the same way as when a non-string arg is received, which indicates
the name of the relationship which had the configurational error.
[ticket:2888]
- :func:`.composite` will raise an informative error message when the
columns/attribute (names) passed don't resolve to a Column or mapped
attribute (such as an erroneous tuple); previously raised an unbound
local. [ticket:2889]