LKi |SSKJrJrJrJrJr SSKJr SSKJ r J r J r SSK J r Jr SSKJr SSKJrJr SSKrSSKrSSKJrJr SS KJr SS KJrJr "S S \ 5r"S S\ \5r"SS\5r \"5r!"SS\RD5r#SS\RHRJS\&S\\&\\S444Sjjr'g))AnyOptionalSequenceTupleType) TracebackType)ProtocolSelfLiteral)ABCabstractmethod)local)overrideEnforceOverridesN)System Component)UUID)islicecountc \rSrSrSrSS\S\\\S4S\ 4Sjjr S \S\ 4S jr SS\S\\ \\S4S\ 4S jjr S\\S44S jrS\ \\S44S jrSrg)CursorzFReifies methods we use from a DBAPI2 Cursor since DBAPI2 is not typed.Nsqlparams.returncgNselfrrs R/var/www/html/dynamic-report/venv/lib/python3.13/site-packages/chromadb/db/base.pyexecuteCursor.execute scriptcgrr)r r&s r! executescriptCursor.executescriptr$r%cgrrrs r! executemanyCursor.executemanys r%cgrrr s r!fetchoneCursor.fetchoner$r%cgrrr.s r!fetchallCursor.fetchallr$r%rr)__name__ __module__ __qualname____firstlineno____doc__strrrrr r"r(rr+r/r2__static_attributes__rr%r!rrsP 3 sCx(A T  C D GK  (%S/)B C   %S/  (5c?3 r%rc r\rSrSrSr\S\4Sj5r\S\\ \ S\\ S\\ S\ S4S j5r S rg ) TxWrapper#a6Wrapper class for DBAPI 2.0 Connection objects, with which clients can implement transactions. Makes two guarantees that basic DBAPI 2.0 connections do not: - __enter__ returns a Cursor object consistently (instead of a Connection like some do) - Always re-raises an exception if one was thrown from the body rcgrrr.s r! __enter__TxWrapper.__enter__+s r%exc_type exc_value tracebackFcgrr)r rArBrCs r!__exit__TxWrapper.__exit__/ r%rN)r4r5r6r7r8r rr?rr BaseExceptionrr rEr:rr%r!r<r<#st 6   4 ./ M* M*     r%r<c\^\rSrSrSrS\4U4Sjjr\S\4Sj5r \ \S\ \ R4Sj55r\ \S\4Sj55r\ \S \\S\\4S j55r\ \S \\S\\4S j55r\ \S\ \4S j55rS\S\ R24SjrSrU=r$)SqlDB9zQDBAPI 2.0 interface wrapper to ensure consistent behavior between implementationssystemc$>[TU]U5 gr)super__init__)r rL __class__s r!rOSqlDB.__init__<s  r%rcg)zReturn a transaction wrapperNrr.s r!txSqlDB.tx?s r%cg)zReturn a PyPika Query builder of an appropriate subtype for this database implementation (see https://pypika.readthedocs.io/en/latest/3_advanced.html#handling-different-database-platforms) Nrrr%r! querybuilderSqlDB.querybuilderDrGr%cg)zReturn the appropriate parameter format for this database implementation. Will be called with str.format(i) where i is the numeric index of the parameter. Nrrr%r!parameter_formatSqlDB.parameter_formatMs r%uuidcg)z=Convert a UUID to a value that can be passed to the DB driverNr)r[s r! uuid_to_dbSqlDB.uuid_to_dbU r%valuecg)z,Convert a value from the DB driver to a UUIDNrr`s r! uuid_from_dbSqlDB.uuid_from_db[r_r%cg)zQReturn the exception type that the DB raises when a unique constraint is violatedNrrr%r!unique_constraint_errorSqlDB.unique_constraint_erroras r%idxch[R"UR5RU55$)z4Return a PyPika Parameter object for the given index)pypika ParameterrYformat)r rhs r!param SqlDB.paramhs' 5 5 7 > >s CDDr%r)r4r5r6r7r8rrOr r<rS staticmethodrrjQueryrVr9rYrrrr]rcrHrfintrkrmr: __classcell__)rPs@r!rJrJ9s*[!v! I   $v||,   c   $ HSM   HSM htn   T-%8  EE!1!1EEr%rJcB\rSrSrSrS\4Sjr\S\S\4Sj5r Sr g ) ParameterValuepz Wrapper class for PyPika paramters that allows the values for Parameters to be expressed inline while building a query. See get_sql() for detailed usage information. r`cXlgrrb)r r`s r!rOParameterValue.__init__ws r%kwargsrc [UR[[45(au[R R UR5 [[R[UR55nSRSU55nSUS3nO_[R RUR5 [RR[[R55n[U5$)Nz, c3`# UH$n[RRU5v M& g7fr)_context formatstrrl).0is r! )ParameterValue.get_sql..s$$S7aX%7%7%>%>q%A%A7s,.()) isinstancer`listtupler{valuesextendr generatorlenjoinappendr|rlnextr9)r rxindexes placeholdersvals r!get_sqlParameterValue.get_sqlzs djj4- 0 0 OO " "4:: .X//TZZAG99$S7$SSLl^1%C OO " "4:: .$$++D1C1C,DEC3xr%rbN) r4r5r6r7r8rrOrr9rr:rr%r!rtrtps5 c    r%rtqueryr|r.c/[l[S5[lU[lUR 5n[ [R5nX#4$)a Wrapper for pypika's get_sql method that allows the values for Parameters to be expressed inline while building a query, and that returns a tuple of the SQL string and parameters. This makes it easier to construct complex queries programmatically and automatically matches up the generated SQL with the required parameter vector. Doing so requires using the ParameterValue class defined in this module instead of the base pypika.Parameter class. Usage Example: q = ( pypika.Query().from_("table") .select("col1") .where("col2"==ParameterValue("foo")) .where("col3"==ParameterValue("bar")) ) sql, params = get_sql(q) cursor.execute(sql, params) Note how it is not necessary to construct the parameter vector manually... it will always be generated with the parameter values in the same order as emitted SQL string. The format string should match the parameter format for the database being used. It will be called with str.format(i) where i is the numeric index of the parameter. For example, Postgres requires parameters like `:1`, `:2`, etc. so the format string should be `":{}"`. See https://pypika.readthedocs.io/en/latest/2_tutorial.html#parametrized-queries for more information on parameterized queries in PyPika. )r{rrrr|rr)rr|rrs r!rrsANHOqH"H --/C 8?? #F ;r%)?)(typingrrrrrtypesrtyping_extensionsr r r abcr r threadingr overridesrrrjpypika.querieschromadb.configrrr[r itertoolsrrrr<rJr{rkrtqueries QueryBuilderr9rrr%r!rs7755#0 -# X * % ,1EI1Eh 7V%%2:=, >> & &,36, 3c3h  ,r%