Error with SQLAlchemy 2.0.0rc1 #687
Comments
baum
pushed a commit
to baum/noobaa-operator
that referenced
this issue
Feb 5, 2023
Default pip installed pykmip-server generates the following error: sqlalchemy.exc.InvalidRequestError: Implicitly combining column managed_objects.uid with column crypto_objects.uid under attribute 'unique_identifier'. Please configure one or more attributes for these same-named columns explicitly. See OpenKMIP/PyKMIP#687 for this workaround Signed-off-by: Alexander Indenbaum <[email protected]>
tangledbytes
pushed a commit
to tangledbytes/noobaa-operator
that referenced
this issue
Feb 9, 2023
Default pip installed pykmip-server generates the following error: sqlalchemy.exc.InvalidRequestError: Implicitly combining column managed_objects.uid with column crypto_objects.uid under attribute 'unique_identifier'. Please configure one or more attributes for these same-named columns explicitly. See OpenKMIP/PyKMIP#687 for this workaround Signed-off-by: Alexander Indenbaum <[email protected]> (cherry picked from commit 1667922)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the requirements.txt file listing the SQLAlchemy requirement using ">=1.0" as the version selector, PyKMIP uses SQLAlchemy 2.0.0rc1.
Upon running pykmip-server, I get the following error:
This error does not appear on changing the SQLAlchemy requirement to "==1.4.45".
The text was updated successfully, but these errors were encountered: