class_docstr: Base class for Operations and BatchOperations.
  
  .. versionadded:: 1.11.0
class_docstr_tok: ["Base","class","for","Operations","and","BatchOperations",".","..","versionadded",":",":","1.11.0"]
docstr: Indicate a string name that has already had a naming convention
  applied to it.
  
  This feature combines with the SQLAlchemy ``naming_convention`` feature
  to disambiguate constraint names that have already had naming
  conventions applied to them, versus those that have not.  This is
  necessary in the case that the ``"%(constraint_name)s"`` token
  is used within a naming convention, so that it can be identified
  that this particular name should remain fixed.
  
  If the :meth:`.Operations.f` is used on a constraint, the naming
  convention will not take effect::
  
      op.add_column("t", "x", Boolean(name=op.f("ck_bool_t_x")))
  
  Above, the CHECK constraint generated will have the name
  ``ck_bool_t_x`` regardless of whether or not a naming convention is
  in use.
  
  Alternatively, if a naming convention is in use, and 'f' is not used,
  names will be converted along conventions.  If the ``target_metadata``
  contains the naming convention
  ``{"ck": "ck_bool_%(table_name)s_%(constraint_name)s"}``, then the
  output of the following:
  
      op.add_column("t", "x", Boolean(name="x"))
  
  will be::
  
      CONSTRAINT ck_bool_t_x CHECK (x in (1, 0)))
  
  The function is rendered in the output of autogenerate when
  a particular constraint name is already converted.
docstr_tok: ["Indicate","a","string","name","that","has","already","had","a","naming","convention","applied","to","it",".","This","feature","combines","with","the","SQLAlchemy","``","naming_convention","``","feature","to","disambiguate","constraint","names","that","have","already","had","naming","conventions","applied","to","them",",","versus","those","that","have","not",".","This","is","necessary","in","the","case","that","the","``","``","%","(","constraint_name",")","s","''","``","token","is","used","within","a","naming","convention",",","so","that","it","can","be","identified","that","this","particular","name","should","remain","fixed",".","If","the",":","meth",":","`",".Operations.f","`","is","used","on","a","constraint",",","the","naming","convention","will","not","take","effect",":",":","op.add_column","(","``","t","''",",","``","x","''",",","Boolean","(","name=op.f","(","``","ck_bool_t_x","''",")",")",")","Above",",","the","CHECK","constraint","generated","will","have","the","name","``","ck_bool_t_x","``","regardless","of","whether","or","not","a","naming","convention","is","in","use",".","Alternatively",",","if","a","naming","convention","is","in","use",",","and","'","f","'","is","not","used",",","names","will","be","converted","along","conventions",".","If","the","``","target_metadata","``","contains","the","naming","convention","``","{","``","ck","''",":","``","ck_bool_","%","(","table_name",")","s_","%","(","constraint_name",")","s","''","}","``",",","then","the","output","of","the","following",":","op.add_column","(","``","t","''",",","``","x","''",",","Boolean","(","name=","''","x","''",")",")","will","be",":",":","CONSTRAINT","ck_bool_t_x","CHECK","(","x","in","(","1",",","0",")",")",")","The","function","is","rendered","in","the","output","of","autogenerate","when","a","particular","constraint","name","is","already","converted","."]
code: def f(self, name: str) -> conv:
      """Indicate a string name that has already had a naming convention
      applied to it.
  
      This feature combines with the SQLAlchemy ``naming_convention`` feature
      to disambiguate constraint names that have already had naming
      conventions applied to them, versus those that have not.  This is
      necessary in the case that the ``"%(constraint_name)s"`` token
      is used within a naming convention, so that it can be identified
      that this particular name should remain fixed.
  
      If the :meth:`.Operations.f` is used on a constraint, the naming
      convention will not take effect::
  
          op.add_column("t", "x", Boolean(name=op.f("ck_bool_t_x")))
  
      Above, the CHECK constraint generated will have the name
      ``ck_bool_t_x`` regardless of whether or not a naming convention is
      in use.
  
      Alternatively, if a naming convention is in use, and 'f' is not used,
      names will be converted along conventions.  If the ``target_metadata``
      contains the naming convention
      ``{"ck": "ck_bool_%(table_name)s_%(constraint_name)s"}``, then the
      output of the following:
  
          op.add_column("t", "x", Boolean(name="x"))
  
      will be::
  
          CONSTRAINT ck_bool_t_x CHECK (x in (1, 0)))
  
      The function is rendered in the output of autogenerate when
      a particular constraint name is already converted.
  
      """
      return conv(name)
  
imports: from __future__ import annotations
  from contextlib import contextmanager
  import re
  import textwrap
  from typing import Any
  from typing import Awaitable
  from typing import Callable
  from typing import Dict
  from typing import Iterator
  from typing import List
  from typing import Mapping
  from typing import NoReturn
  from typing import Optional
  from typing import overload
  from typing import Sequence
  from typing import Tuple
  from typing import Type
  from typing import TYPE_CHECKING
  from typing import TypeVar
  from typing import Union
  from sqlalchemy.sql.elements import conv
  from .None import batch
  from .None import schemaobj
  from ..None import util
  from ..util import sqla_compat
  from ..util.compat import formatannotation_fwdref
  from ..util.compat import inspect_formatargspec
  from ..util.compat import inspect_getfullargspec
  from ..util.sqla_compat import _literal_bindparam
label_desc: Use image node_id 11 for calling the AbstractOperations obj's underlying member method code with example usage: obj.f(name) and returns: conv