convert_unicode logic disabled in the sqlite dialect,
to adjust for pysqlite 2.5.0's new requirement that
only Python unicode objects are accepted;
- https://itsystementwicklung.de/pipermail/list-pysqlite/2008-March/000018.html
+ https://web.archive.org/web/20090614054912/https://itsystementwicklung.de/pipermail/list-pysqlite/2008-March/000018.html
.. change::
:tags: oracle
logic disabled in the sqlite dialect, to adjust for pysqlite
2.5.0's new requirement that only Python unicode objects are
accepted;
- https://itsystementwicklung.de/pipermail/list-pysqlite/2008-March/000018.html
+ http://web.archive.org/web/20090614054912/https://itsystementwicklung.de/pipermail/list-pysqlite/2008-March/000018.html
.. change::
:tags: mysql
ready for general use yet, however
it does have *extremely* rudimental
functionality now.
- https://bitbucket.org/zzzeek/sqlalchemy-access
+ https://github.com/gordthompson/sqlalchemy-access
.. change::
:tags: maxdb, moved
The MaxDB dialect, which hasn't been
functional for several years, is
- moved out to a pending bitbucket project,
- https://bitbucket.org/zzzeek/sqlalchemy-maxdb.
+ moved out to a pending bitbucket project, (deleted; to view
+ the MaxDB code see the commit before it was removed at
+ https://github.com/sqlalchemy/sqlalchemy/tree/ba67f7dbc5eb7a1ed2a3e1b56df72a837130f7bb/lib/sqlalchemy/dialects/maxdb)
.. change::
:tags: sqlite, feature
Important Dialect Links:
* Documentation on connect arguments:
- https://www.sqlalchemy.org/docs/06/dbengine.html#create-
- engine-url-arguments.
+ https://www.sqlalchemy.org/docs/06/dbengine.html#create-engine-url-arguments.
-* Reference documentation for individual dialects: https://ww
- w.sqlalchemy.org/docs/06/reference/dialects/index.html
+* Reference documentation for individual dialects:
+ https://www.sqlalchemy.org/docs/06/reference/dialects/index.html.
* The tips and tricks at DatabaseNotes.
SQLSoup has been modernized and updated to reflect common
0.5/0.6 capabilities, including well defined session
-integration. Please read the new docs at [https://www.sqlalc
-hemy.org/docs/06/reference/ext/sqlsoup.html].
+integration. Please read the new docs at
+[https://www.sqlalchemy.org/docs/06/reference/ext/sqlsoup.html].
Declarative
-----------
A demonstration of callcount reduction including a sample
benchmark script is at
-https://techspot.zzzeek.org/2010/12/12/a-tale-of-three-
-profiles/
+https://techspot.zzzeek.org/2010/12/12/a-tale-of-three-profiles/
Composites Rewritten
--------------------
SQLSoup is a handy package that presents an alternative
interface on top of the SQLAlchemy ORM. SQLSoup is now
moved into its own project and documented/released
-separately; see https://bitbucket.org/zzzeek/sqlsoup.
+separately; see https://github.com/zzzeek/sqlsoup.
SQLSoup is a very simple tool that could also benefit from
contributors who are interested in its style of usage.
It is hoped that the :class:`.AutomapBase` system provides a quick
and modernized solution to the problem that the very famous
-`SQLSoup <https://sqlsoup.readthedocs.io/en/latest/>`_
+`SQLSoup <https://pypi.org/project/sqlsoup/>`_
also tries to solve, that of generating a quick and rudimentary object
model from an existing database on the fly. By addressing the issue strictly
at the mapper configuration level, and integrating fully with existing
Drizzle Dialect is now an External Dialect
------------------------------------------
-The dialect for `Drizzle <https://www.drizzle.org/>`_ is now an external
+The dialect for `Drizzle <https://en.wikipedia.org/wiki/Drizzle_(database_server)>`_ is now an external
dialect, available at https://bitbucket.org/zzzeek/sqlalchemy-drizzle.
This dialect was added to SQLAlchemy right before SQLAlchemy was able to
accommodate third party dialects well; going forward, all databases that aren't
However, there are many constructs that are specific to some particular kind
of database dialect, for which the :class:`.StrSQLCompiler` doesn't know how
to turn into a string, such as the PostgreSQL
-`"insert on conflict" <postgresql_insert_on_conflict>`_ construct::
+:ref:`postgresql_insert_on_conflict` construct::
>>> from sqlalchemy.dialects.postgresql import insert
>>> from sqlalchemy import table, column
Oracle doesn't have native ON UPDATE CASCADE functionality. A trigger based
solution is available at
-https://asktom.oracle.com/tkyte/update_cascade/index.html .
+https://web.archive.org/web/20090317041251/https://asktom.oracle.com/tkyte/update_cascade/index.html
When using the SQLAlchemy ORM, the ORM has limited ability to manually issue
cascading updates - specify ForeignKey objects using the
# oracle has no ON UPDATE CASCADE -
# its only available via triggers
- # https://asktom.oracle.com/tkyte/update_cascade/index.html
+ # https://web.archive.org/web/20090317041251/https://asktom.oracle.com/tkyte/update_cascade/index.html
if constraint.onupdate is not None:
util.warn(
"Oracle does not contain native UPDATE CASCADE "
It is hoped that the :class:`.AutomapBase` system provides a quick
and modernized solution to the problem that the very famous
-`SQLSoup <https://sqlsoup.readthedocs.io/en/latest/>`_
+`SQLSoup <https://pypi.org/project/sqlsoup/>`_
also tries to solve, that of generating a quick and rudimentary object
model from an existing database on the fly. By addressing the issue strictly
at the mapper configuration level, and integrating fully with existing
projects / thirdparty / sqlalchemy / sqlalchemy.git / commitdiff
