Piccolo

------

* Fixed a bug with nullable ``JSON`` / ``JSONB`` columns and
``create_pydantic_model`` - thanks to eneacosta for this fix.
* Made the ``Time`` column type importable from ``piccolo.columns``.
* Python 3.11 is now supported.
* Postgres 9.6 is no longer officially supported, as it's end of life, but
Piccolo should continue to work with it just fine for now.
* Improved docs for transactions, added docs for the ``as_of`` clause in
CockroachDB (thanks to gnat for this), and added docs for
``add_raw_backwards``.

-------------------------------------------------------------------------------

------

Added initial support for Cockroachdb (thanks to gnat for this massive
contribution).

Fixed Pylance warnings (thanks to MiguelGuthridge for this).

-------------------------------------------------------------------------------

------

Added support for Starlite. If you use ``piccolo asgi new`` you'll see it as
an option for a router.

Thanks to sinisaos for adding this, and peterschutt for helping debug ASGI
mounting.

-------------------------------------------------------------------------------

------

Fixed an edge case, where a migration could fail if:

* 5 or more tables were being created at once.
* They all contained foreign keys to each other, as shown below.

.. code-block:: python

class TableA(Table):
pass

class TableB(Table):
fk = ForeignKey(TableA)

class TableC(Table):
fk = ForeignKey(TableB)

class TableD(Table):
fk = ForeignKey(TableC)

class TableE(Table):
fk = ForeignKey(TableD)


Thanks to sumitsharansatsangi for reporting this issue.

-------------------------------------------------------------------------------

------

Made it easier to access the ``Email`` columns on a table.

.. code-block:: python

>>> MyTable._meta.email_columns
[MyTable.email_column_1, MyTable.email_column_2]

This was added for Piccolo Admin.

-------------------------------------------------------------------------------

------

Fixed a bug with migrations - when using ``db_column_name`` it wasn't being
used in some alter statements. Thanks to theelderbeever for reporting this
issue.

.. code-block:: python

class Concert(Table):
We use `db_column_name` when the column name is problematic - e.g. if
it clashes with a Python keyword.
in_ = Varchar(db_column_name='in')

-------------------------------------------------------------------------------