a c g+@sddlmZddlmZddlmZddlmZddlmZddlmZddlmZddlm Z dd lm Z dd lm Z dd lm Z dd lm Z d dlmZd dlmZdZGdddejjZGdddeZGdddejZGdddeZdS))ARRAY)array)ASTEXT) CONTAINED_BY)CONTAINS) DELETE_PATH)HAS_ALL)HAS_ANY)HAS_KEY)JSONPATH_ASTEXT) PATH_EXISTS) PATH_MATCH)types)cast)JSONJSONBc@s$eZdZddZddZddZdS) JSONPathTypecsfdd}|S)Ncs<t|tr|S|r(ddtt|}nd}r8|}|S)Nz{%s}z, z{}) isinstancestrjoinmap)value super_procf/var/www/html/llm_bihealth/app/venv/lib/python3.9/site-packages/sqlalchemy/dialects/postgresql/json.pyprocesss z(JSONPathType._processor..processr)selfdialectrrrrr _processors zJSONPathType._processorcCs||||SN)r Zstring_bind_processorrrrrrbind_processor/szJSONPathType.bind_processorcCs||||Sr!)r Zstring_literal_processorr"rrrliteral_processor2szJSONPathType.literal_processorN)__name__ __module__ __qualname__r r#r$rrrrrsrc@seZdZdZdZdS)JSONPATHadJSON Path Type. This is usually required to cast literal values to json path when using json search like function, such as ``jsonb_path_query_array`` or ``jsonb_path_exists``:: stmt = sa.select( sa.func.jsonb_path_query_array( table.c.jsonb_col, cast("$.address.id", JSONPATH) ) ) N)r%r&r'__doc____visit_name__rrrrr(6sr(csBeZdZdZeZdfdd ZGdddejj Z e Z Z S) ra Represent the PostgreSQL JSON type. :class:`_postgresql.JSON` is used automatically whenever the base :class:`_types.JSON` datatype is used against a PostgreSQL backend, however base :class:`_types.JSON` datatype does not provide Python accessors for PostgreSQL-specific comparison methods such as :meth:`_postgresql.JSON.Comparator.astext`; additionally, to use PostgreSQL ``JSONB``, the :class:`_postgresql.JSONB` datatype should be used explicitly. .. seealso:: :class:`_types.JSON` - main documentation for the generic cross-platform JSON datatype. The operators provided by the PostgreSQL version of :class:`_types.JSON` include: * Index operations (the ``->`` operator):: data_table.c.data['some key'] data_table.c.data[5] * Index operations returning text (the ``->>`` operator):: data_table.c.data['some key'].astext == 'some value' Note that equivalent functionality is available via the :attr:`.JSON.Comparator.as_string` accessor. * Index operations with CAST (equivalent to ``CAST(col ->> ['some key'] AS )``):: data_table.c.data['some key'].astext.cast(Integer) == 5 Note that equivalent functionality is available via the :attr:`.JSON.Comparator.as_integer` and similar accessors. * Path index operations (the ``#>`` operator):: data_table.c.data[('key_1', 'key_2', 5, ..., 'key_n')] * Path index operations returning text (the ``#>>`` operator):: data_table.c.data[('key_1', 'key_2', 5, ..., 'key_n')].astext == 'some value' Index operations return an expression object whose type defaults to :class:`_types.JSON` by default, so that further JSON-oriented instructions may be called upon the result type. Custom serializers and deserializers are specified at the dialect level, that is using :func:`_sa.create_engine`. The reason for this is that when using psycopg2, the DBAPI only allows serializers at the per-cursor or per-connection level. E.g.:: engine = create_engine("postgresql+psycopg2://scott:tiger@localhost/test", json_serializer=my_serialize_fn, json_deserializer=my_deserialize_fn ) When using the psycopg2 dialect, the json_deserializer is registered against the database using ``psycopg2.extras.register_default_json``. .. seealso:: :class:`_types.JSON` - Core level JSON type :class:`_postgresql.JSONB` FNcs tj|d|dur||_dS)a|Construct a :class:`_types.JSON` type. :param none_as_null: if True, persist the value ``None`` as a SQL NULL value, not the JSON encoding of ``null``. Note that when this flag is False, the :func:`.null` construct can still be used to persist a NULL value:: from sqlalchemy import null conn.execute(table.insert(), data=null()) .. seealso:: :attr:`_types.JSON.NULL` :param astext_type: the type to use for the :attr:`.JSON.Comparator.astext` accessor on indexed attributes. Defaults to :class:`_types.Text`. ) none_as_nullN)super__init__ astext_type)rr+r. __class__rrr-sz JSON.__init__c@seZdZdZeddZdS)zJSON.Comparator6Define comparison operations for :class:`_types.JSON`.cCsPt|jjjtjjr0|jjjt |jj|jj dS|jjjt |jj|jj dSdS)aOn an indexed expression, use the "astext" (e.g. "->>") conversion when rendered in SQL. E.g.:: select(data_table.c.data['some key'].astext) .. seealso:: :meth:`_expression.ColumnElement.cast` Z result_typeN) rexprrighttypesqltypesrrleftoperater r.r)rrrrastextszJSON.Comparator.astextN)r%r&r'r)propertyr9rrrr Comparatorsr;)FN) r%r&r'r)r6Textr.r-rr;comparator_factory __classcell__rrr/rrHs Jrc@s*eZdZdZdZGdddejZeZdS)ra Represent the PostgreSQL JSONB type. The :class:`_postgresql.JSONB` type stores arbitrary JSONB format data, e.g.:: data_table = Table('data_table', metadata, Column('id', Integer, primary_key=True), Column('data', JSONB) ) with engine.connect() as conn: conn.execute( data_table.insert(), data = {"key1": "value1", "key2": "value2"} ) The :class:`_postgresql.JSONB` type includes all operations provided by :class:`_types.JSON`, including the same behaviors for indexing operations. It also adds additional operators specific to JSONB, including :meth:`.JSONB.Comparator.has_key`, :meth:`.JSONB.Comparator.has_all`, :meth:`.JSONB.Comparator.has_any`, :meth:`.JSONB.Comparator.contains`, :meth:`.JSONB.Comparator.contained_by`, :meth:`.JSONB.Comparator.delete_path`, :meth:`.JSONB.Comparator.path_exists` and :meth:`.JSONB.Comparator.path_match`. Like the :class:`_types.JSON` type, the :class:`_postgresql.JSONB` type does not detect in-place changes when used with the ORM, unless the :mod:`sqlalchemy.ext.mutable` extension is used. Custom serializers and deserializers are shared with the :class:`_types.JSON` class, using the ``json_serializer`` and ``json_deserializer`` keyword arguments. These must be specified at the dialect level using :func:`_sa.create_engine`. When using psycopg2, the serializers are associated with the jsonb type using ``psycopg2.extras.register_default_jsonb`` on a per-connection basis, in the same way that ``psycopg2.extras.register_default_json`` is used to register these handlers with the json type. .. seealso:: :class:`_types.JSON` c@sPeZdZdZddZddZddZdd Zd d Zd d Z ddZ ddZ dS)zJSONB.Comparatorr1cCs|jt|tjdS)zvBoolean expression. Test for presence of a key. Note that the key may be a SQLA expression. r2)r8r r6Booleanrotherrrrhas_keyszJSONB.Comparator.has_keycCs|jt|tjdS)z;Boolean expression. Test for presence of all keys in jsonbr2)r8rr6r?r@rrrhas_allszJSONB.Comparator.has_allcCs|jt|tjdS)z:Boolean expression. Test for presence of any key in jsonbr2)r8r r6r?r@rrrhas_any szJSONB.Comparator.has_anycKs|jt|tjdS)zBoolean expression. Test if keys (or array) are a superset of/contained the keys of the argument jsonb expression. kwargs may be ignored by this operator but are required for API conformance. r2)r8rr6r?)rrAkwargsrrrcontainsszJSONB.Comparator.containscCs|jt|tjdS)z|Boolean expression. Test if keys are a proper subset of the keys of the argument jsonb expression. r2)r8rr6r?r@rrr contained_byszJSONB.Comparator.contained_bycCs2t|tst|}t|ttj}|jt|tdS)aJSONB expression. Deletes field or array element specified in the argument array. The input may be a list of strings that will be coerced to an ``ARRAY`` or an instance of :meth:`_postgres.array`. .. versionadded:: 2.0 r2) r _pg_arrayrrr6ZTEXTr8rr)rrZ right_siderrr delete_path!s zJSONB.Comparator.delete_pathcCs|jt|tjdS)zBoolean expression. Test for presence of item given by the argument JSONPath expression. .. versionadded:: 2.0 r2)r8r r6r?r@rrr path_exists/szJSONB.Comparator.path_existscCs|jt|tjdS)zBoolean expression. Test if JSONPath predicate given by the argument JSONPath expression matches. Only the first item of the result is taken into account. .. versionadded:: 2.0 r2)r8r r6r?r@rrr path_match9szJSONB.Comparator.path_matchN) r%r&r'r)rBrCrDrFrGrIrJrKrrrrr;s  r;N)r%r&r'r)r*rr;r=rrrrrs0FrN)rrrH operatorsrrrrrr r r r r rr6Zsqlr__all__rrr(rrrrr s&