-hB*SSKJr SSKJr SSKJr SSKJr Sr\R\Rr \R"S\ SSS 9r \R"S \ SSS 9r\R"S \ SSS 9r\R"S \ SSS 9r\R"S \ SSS 9r\R"S\ SSS 9r\R"S\ SSS 9r"SS\R(R*5r"SS\R(5r"SS\5rg))absolute_import)types)util) operators)JSONJSONBz->>T) precedencenatural_self_precedenteager_groupingz#>>?z?&z?|z@>z<@c \rSrSrSrSrSrg) JSONPathTypeEc6^URU5mU4SjnU$)Nc>[U[RR5(deUVs/sHn[R"U5PM nnSSR U5-nT(aT"U5nU$s snfNz{%s}z,  isinstancercollections_abcSequence text_typejoinvalueelemtokens super_procs xC:\Users\ROHAN GUPTA\OneDrive\Desktop\mathbuddy-assessment\venv\Lib\site-packages\sqlalchemy/dialects/postgresql/json.pyprocess,JSONPathType.bind_processor..processIieT%9%9%B%BCC CC7<=utdnnT*uF=dii/0E"5)L > A8)string_bind_processorselfdialectr rs @rbind_processorJSONPathType.bind_processorFs//8  c6^URU5mU4SjnU$)Nc>[U[RR5(deUVs/sHn[R"U5PM nnSSR U5-nT(aT"U5nU$s snfrrrs rr /JSONPathType.literal_processor..processVr"r#)string_literal_processorr%s @rliteral_processorJSONPathType.literal_processorSs227;  r*N)__name__ __module__ __qualname____firstlineno__r(r/__static_attributes__r1r*rrrEs   r*rc^\rSrSrSr\R "5rSU4Sjjr"SS\RR5r \ r Sr U=r $)raa 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' .. versionchanged:: 1.1 The :meth:`_expression.ColumnElement.cast` operator on JSON objects now requires that the :attr:`.JSON.Comparator.astext` modifier be called explicitly, if the cast works only from a textual string. 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://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` .. versionchanged:: 1.1 :class:`_postgresql.JSON` is now a PostgreSQL- specific specialization of the new :class:`_types.JSON` type. c<>[[U] US9 UbX lgg)aConstruct 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()) .. versionchanged:: 0.9.8 - Added ``none_as_null``, and :func:`.null` is now supported in order to persist a NULL value. .. 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`. .. versionadded:: 1.1 ) none_as_nullN)superr__init__ astext_type)r&r:r= __class__s rr< JSON.__init__s(2 dD" "=  "*  #r*c(\rSrSrSr\S5rSrg)JSON.Comparator6Define comparison operations for :class:`_types.JSON`.c[URRR[R R 5(aQURRR[URRURRS9$URRR[URRURRS9$)zOn 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`  result_type) rexprrighttypesqltypesrrleftoperateJSONPATH_ASTEXTr=ASTEXT)r&s rastextJSON.Comparator.astexts$))//.. 0J0JKKyy~~--#IIOO $ 5 5. yy~~--DIIOO9N9N.r*r1N)r2r3r4r5__doc__propertyrOr6r1r*r ComparatorrAsD    r*rS)r=)FN)r2r3r4r5rQrJTextr=r<rrScomparator_factoryr6 __classcell__)r>s@rrras:Qf--/K+:X]]--8$r*rcJ\rSrSrSrSr"SS\R5r\rSr g)r aRepresent 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`, and :meth:`.JSONB.Comparator.contained_by`. 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. .. versionadded:: 0.9.7 .. seealso:: :class:`_types.JSON` c6\rSrSrSrSrSrSrSrSr Sr g ) JSONB.Comparatori%rCcHUR[U[RS9$)zBoolean expression. Test for presence of a key (equivalent of the ``?`` operator). Note that the key may be a SQLA expression. rE)rLHAS_KEYrJBooleanr&others rhas_keyJSONB.Comparator.has_key(<<H`` operator). kwargs may be ignored by this operator but are required for API conformance. rE)rLCONTAINSrJr])r&r_kwargss rcontainsJSONB.Comparator.contains:s<<%X=M=M<N Nr*cHUR[U[RS9$)zBoolean expression. Test if keys are a proper subset of the keys of the argument jsonb expression (equivalent of the ``<@`` operator). rE)rL CONTAINED_BYrJr]r^s r contained_byJSONB.Comparator.contained_byDs' <<e1A1A  r*r1N) r2r3r4r5rQr`rerirnrrr6r1r*rrSrZ%s"D N  N  N  O r*rSr1N) r2r3r4r5rQ__visit_name__rrSrUr6r1r*rr r s(-^N&T__&P$r*r N) __future__rrrJrsqlr__all__ _PRECEDENCEjson_getitem_opidx_precedence custom_oprNrMr\rdrhrlrqrrr r1r*rr}s7'! &&y'@'@A      %%                      ""  8==--8O$8==O$dZ$DZ$r*