PR #619 completely removed support for compare_against_backend, but it's still documented
#1293
Labels
Milestone
Comments
CaselIT
changed the title
compare_against_backend, but it's still documented and supposedly testedcompare_against_backend, but it's still documented
|
we never fixed this; removing from the docs now |
|
Mike Bayer has proposed a fix for this issue in the main branch: remove compare_against_backend from tests and docs https://gerrit.sqlalchemy.org/c/sqlalchemy/alembic/+/4925 |
sqlalchemy-bot
pushed a commit
to sqlalchemy/sqlalchemy
that referenced
this issue
Oct 20, 2023
Removed unused placeholder method :meth:`.TypeEngine.compare_against_backend` This method was used by very old versions of Alembic. See sqlalchemy/alembic#1293 for details. Follow up of alembic change I6f480711ec94cd4113d3f0ca114d143b49b8d869 Change-Id: I48ba2b26128ba6f74cb0b2c54caa6f7d2a711257
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The PR #619 has completely removed support for
compare_against_backend, but it's still documented and supposedly tested (the test is clearly broken.)@zzzeek This seems to be a rarely used feature, since no-one reported it, but since it's still documented and all it may be better to just re-introduce it. If you feel like it make more sense removing it, then this issue could be used to remove the docs for it
Originally posted by @CaselIT in #619 (comment)
The text was updated successfully, but these errors were encountered: