Fixed #23061: Avoided setting a limit on a query for get with select_for_update on Oracle

    uppercases_column_names = False

    # Does the backend support "select for update" queries with limit (and offset)?

    supports_select_for_update_with_limit = True

    def __init__(self, connection):

        self.connection = connection

    closed_cursor_error_class = InterfaceError

    bare_select_suffix = " FROM DUAL"

    uppercases_column_names = True

    # select for update with limit can be achieved on Oracle, but not with the current backend.

    supports_select_for_update_with_limit = False

class DatabaseOperations(BaseDatabaseOperations):

        clone = self.filter(*args, **kwargs)

        if self.query.can_filter():

            clone = clone.order_by()

        if (not clone.query.select_for_update or

            connections[self.db].features.supports_select_for_update_with_limit):

            clone = clone[:MAX_GET_RESULTS + 1]

        num = len(clone)

        if num == 1:

            self.assertEqual(router.db_for_write(Person), query.db)

        finally:

            router.routers = old_routers

    @skipUnlessDBFeature('has_select_for_update')

    def test_select_for_update_with_get(self):

        with transaction.atomic():

            person = Person.objects.select_for_update().get(name='Reinhardt')

        self.assertEqual(person.name, 'Reinhardt')