HEX
Server: Apache/2.4.52 (Ubuntu)
System: Linux spn-python 5.15.0-89-generic #99-Ubuntu SMP Mon Oct 30 20:42:41 UTC 2023 x86_64
User: arjun (1000)
PHP: 8.1.2-1ubuntu2.20
Disabled: NONE
Upload Files
File: //usr/local/lib/python3.10/dist-packages/sqlalchemy/dialects/mssql/__pycache__/json.cpython-310.pyc
o

���g��@s\ddlmZGdd�dej�ZGdd�d�ZGdd�deejj�ZGdd	�d	eejj�Zd
S)�)�typesc@seZdZdZdS)�JSONa�	MSSQL JSON type.

    MSSQL supports JSON-formatted data as of SQL Server 2016.

    The :class:`_mssql.JSON` datatype at the DDL level will represent the
    datatype as ``NVARCHAR(max)``, but provides for JSON-level comparison
    functions as well as Python coercion behavior.

    :class:`_mssql.JSON` is used automatically whenever the base
    :class:`_types.JSON` datatype is used against a SQL Server backend.

    .. seealso::

        :class:`_types.JSON` - main documentation for the generic
        cross-platform JSON datatype.

    The :class:`_mssql.JSON` type supports persistence of JSON values
    as well as the core index operations provided by :class:`_types.JSON`
    datatype, by adapting the operations to render the ``JSON_VALUE``
    or ``JSON_QUERY`` functions at the database level.

    The SQL Server :class:`_mssql.JSON` type necessarily makes use of the
    ``JSON_QUERY`` and ``JSON_VALUE`` functions when querying for elements
    of a JSON object.   These two functions have a major restriction in that
    they are **mutually exclusive** based on the type of object to be returned.
    The ``JSON_QUERY`` function **only** returns a JSON dictionary or list,
    but not an individual string, numeric, or boolean element; the
    ``JSON_VALUE`` function **only** returns an individual string, numeric,
    or boolean element.   **both functions either return NULL or raise
    an error if they are not used against the correct expected value**.

    To handle this awkward requirement, indexed access rules are as follows:

    1. When extracting a sub element from a JSON that is itself a JSON
       dictionary or list, the :meth:`_types.JSON.Comparator.as_json` accessor
       should be used::

            stmt = select(data_table.c.data["some key"].as_json()).where(
                data_table.c.data["some key"].as_json() == {"sub": "structure"}
            )

    2. When extracting a sub element from a JSON that is a plain boolean,
       string, integer, or float, use the appropriate method among
       :meth:`_types.JSON.Comparator.as_boolean`,
       :meth:`_types.JSON.Comparator.as_string`,
       :meth:`_types.JSON.Comparator.as_integer`,
       :meth:`_types.JSON.Comparator.as_float`::

            stmt = select(data_table.c.data["some key"].as_string()).where(
                data_table.c.data["some key"].as_string() == "some string"
            )

    .. versionadded:: 1.4


    N)�__name__�
__module__�__qualname__�__doc__�rr�I/usr/local/lib/python3.10/dist-packages/sqlalchemy/dialects/mssql/json.pyrsrc@s$eZdZdd�Zdd�Zdd�ZdS)�_FormatTypeMixincCst���N)�NotImplementedError��self�valuerrr	�
_format_valueUsz_FormatTypeMixin._format_valuec���|����fdd�}|S)Nc���|�}�r�|�}|Sr�r�r�r�
super_procrr	�process[�
z0_FormatTypeMixin.bind_processor.<locals>.process)�string_bind_processor�r�dialectrrrr	�bind_processorX�
z_FormatTypeMixin.bind_processorcr)Ncrrrrrrr	rfrz3_FormatTypeMixin.literal_processor.<locals>.process)�string_literal_processorrrrr	�literal_processorcrz"_FormatTypeMixin.literal_processorN)rrrrrrrrrr	r
Tsr
c@�eZdZdd�ZdS)�
JSONIndexTypecCs"t|t�rd|}|Sd|}|S)Nz$[%s]z$."%s"��
isinstance�intr
rrr	rps

�zJSONIndexType._format_valueN�rrrrrrrr	r!o�r!c@r )�JSONPathTypecCsdd�dd�|D��S)Nz$%s�cSs&g|]}t|t�r
d|nd|�qS)z[%s]z."%s"r")�.0�elemrrr	�
<listcomp>|s��z.JSONPathType._format_value.<locals>.<listcomp>)�joinr
rrr	rys���zJSONPathType._format_valueNr%rrrr	r'xr&r'N)r(r�sqltypesrr
r!r'rrrr	�<module>s

A