rjJdddlmZddlmZddlmZddlmZddlmZddl m Z ddl m Z dd l m Z erdd lmZdd lmZdd lmZed eZGddej(e ZGddZGddeej(j,ZGddeej(j.Zy)) annotations)Any) TYPE_CHECKING)TypeVar)types)_NoArg)NO_ARG)_T_JSON)Dialect)_BindProcessorType)_LiteralProcessorType_T)boundc<eZdZUdZded<def dfd ZxZS)JSONa Oracle JSON type. .. versionadded:: 2.1 Oracle Database supports JSON storage and querying for character and BLOB datatypes in Oracle 12c, and supports a dedicated JSON data type as of Oracle 21c. SQLAlchemy supports both of these scenarios when using the oracledb DBAPI. This type is used implicitly whenever the base :class:`_types.JSON` datatype is used against an Oracle backend, or may be constructed directly for access to Oracle-specific parameters such as :paramref:`_oracle.JSON.use_blob`. Index operations are adapted to render using the ``JSON_QUERY`` and ``JSON_VALUE`` functions at the database level. **Platform Support** - When using Oracle Database versions prior to 21c, BLOB is used as the storage format. In 21c or later, the native JSON datatype is used. This can be overridden using the :paramref:`_oracle.JSON.use_blob` parameter. **Serialization / Deserialization** - JSON serialization of bound parameters uses Python ``json.dumps()`` by default rather than oracledb's native serializer, in order to support the :paramref:`_sqltypes.JSON.none_as_null` feature. The default serializer does **not** accept Python ``Decimal`` objects; to use a custom serializer, pass :paramref:`_sa.create_engine.json_serializer` to :func:`_sa.create_engine`. When using the native JSON datatype (21c+), deserialization uses oracledb's native deserializer by default, which is required for JSON values larger than 32767 bytes. However, this deserializer returns all numeric values as ``Decimal`` since Oracle Database stores JSON numbers using its internal NUMBER type. To receive standard Python numeric types, pass ``json_deserializer=json.loads`` via :paramref:`_sa.create_engine.json_deserializer`; note that this limits maximum JSON value size to 32767 bytes. When using BLOB storage, SQLAlchemy deserializes using ``json.loads()`` directly rather than the oracledb deserializer. **CHECK Constraint with BLOB** - When using BLOB storage, either on Oracle Database versions prior to 21c or via the :paramref:`_oracle.JSON.use_blob` parameter, the oracledb driver documentation recommends adding a `` IS JSON`` check constraint to indicate to the driver that the column stores JSON data. This constraint is **not** automatically generated by :class:`_oracle.JSON` and is not required by SQLAlchemy's implementation in order to read JSON data from the column. If desired, it can be added explicitly using :class:`_schema.CheckConstraint`. .. seealso:: :class:`_types.JSON` - main documentation for the generic cross-platform JSON datatype. bool | _NoArguse_blobFc4t||||_y)aConstruct a :class:`_oracle.JSON` type. :param none_as_null=False: if True, persist the value ``None`` as a SQL NULL value, not the JSON encoding of ``null``. See the notes at :paramref:`_sqltypes.JSON.none_as_null` for complete background on this option. :param use_blob: A boolean parameter indicating if the type should be rendered in DDL using BLOB instead of JSON. Normally, JSON or BLOB is chosen automatically based on the version of Oracle in use (21c or greater for JSON). If the parameter is left at its default value of the ``NO_ARG`` constant, this automatic selection is used. However when ``True``, the BLOB datatype will be used unconditionally, and if ``False``, JSON will be used unconditionally (including on backends older than 21c, which will raise an error by the server. This may be used to assert that only JSON-supporting backends should be used). ) none_as_nullN)super__init__r)selfrr __class__s j/var/www/html/python-recuperauto-other/env/lib/python3.12/site-packages/sqlalchemy/dialects/oracle/json.pyrz JSON.__init__Vs. l3  )rboolrr)__name__ __module__ __qualname____doc____annotations__r r __classcell__)rs@rrrs25n$)F! !4A!!rrc,eZdZddZddZ ddZy)_FormatTypeMixinctN)NotImplementedErrorrvalues r _format_valuez_FormatTypeMixin._format_valuers !##rc:j|dfd }|S)Nc>j|}r|}|Sr'r+r*r super_procs rprocessz0_FormatTypeMixin.bind_processor..processx%&&u-E"5)Lr)r*rreturnr)string_bind_processorrdialectr1r0s` @rbind_processorz_FormatTypeMixin.bind_processorus//8   rc:j|dfd }|S)Nc>j|}r|}|Sr'r.r/s rr1z3_FormatTypeMixin.literal_processor..processr2rr*rr3str)string_literal_processorr5s` @rliteral_processorz"_FormatTypeMixin.literal_processors!227;   rNr:)r6r r3z_BindProcessorType[Any])r6r r3z_LiteralProcessorType[Any])rrr r+r7r=rrr%r%qs!$    # rr%ceZdZddZy) JSONIndexTypec:t|trd|dSd|dS)Nz$[]z$."" isinstanceintr)s rr+zJSONIndexType._format_values( eS !wa= q> !rNr:rrr r+r>rrr@r@s"rr@ceZdZddZy) JSONPathTypec8ddjd|DzS)Nz$%sc3TK|] }t|trd|dnd|d"yw)[rBz."rCNrD).0elems r z-JSONPathType._format_value..s6 *$4!D6 BtfA,Fs&()joinr)s rr+zJSONPathType._format_values( GG!   rNr:rGr>rrrIrIs rrIN) __future__rtypingrrrrKrsqltypessql.baser r sql.sqltypesr engine.interfacesr sql.type_apir rrrr%r@rIr>rrrYs# !#,25 TR!8== !R!j:"$hmm&A&A" #X]]%?%? r