ug ddlmZmZmZmZmZmZddlmZddl m Z m Z m Z ddl mZmZddlmZddlmZmZddlZddlZddlmZmZdd lmZdd lmZmZdd lm Z Gd d e Z!GddeeZ"GddeZ#eZ$GddejJZ& ddejNjPde)dee)eedfffdZ*y))AnyOptionalSequenceTupleTypeUnion) TracebackType)ProtocolSelfLiteral)ABCabstractmethod)local)overrideEnforceOverridesN)System Component)UUID)islicecount)SeqIdc eZdZdZd dedeeedfdefdZ dedefd Z d dedee eedfdefd Z deedffd Z de eedffd Zy)CursorzFReifies methods we use from a DBAPI2 Cursor since DBAPI2 is not typed.Nsqlparams.returncyNselfrrs E/var/www/openai/venv/lib/python3.12/site-packages/chromadb/db/base.pyexecutezCursor.execute scriptcyrr)r!r&s r" executescriptzCursor.executescriptr$r%cyrrr s r" executemanyzCursor.executemanys r%cyrrr!s r"fetchonezCursor.fetchoner$r%cyrrr,s r"fetchallzCursor.fetchall r$r%r)__name__ __module__ __qualname____doc__strrrrr r#r(rr*r-r/rr%r"rrsP 3 sCx(A T  C D GK  (%S/)B C   %S/  (5c?3 r%rc feZdZdZedefdZedeee dee dee de dfdZ y ) TxWrapperaFWrapper 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 rcyrrr,s r" __enter__zTxWrapper.__enter__,s r%exc_type exc_value tracebackFcyrr)r!r9r:r;s r"__exit__zTxWrapper.__exit__0 r%N) r0r1r2r3rrr8rr BaseExceptionr r r=rr%r"r6r6$st 6   4 ./ M* M*     r%r6ceZdZdZdeffd ZedefdZe ede e jfdZ e edefdZe edeedeefd Ze ed eedeefd Ze ede efd Zd ede j0fdZe deeefdefdZe dedefdZxZS)SqlDBzQDBAPI 2.0 interface wrapper to ensure consistent behavior between implementationssystemc$t||yr)super__init__)r!rB __class__s r"rEzSqlDB.__init__=s  r%rcy)zReturn a transaction wrapperNrr,s r"txzSqlDB.tx@s r%cy)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" querybuilderzSqlDB.querybuilderEr>r%cy)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_formatzSqlDB.parameter_formatNs r%uuidcy)z=Convert a UUID to a value that can be passed to the DB driverNr)rMs r" uuid_to_dbzSqlDB.uuid_to_dbV r%valuecy)z,Convert a value from the DB driver to a UUIDNrrQs r" uuid_from_dbzSqlDB.uuid_from_db\rPr%cy)zYReturn the exception type that the DB raises when a unique constraint is violatedNrrr%r"unique_constraint_errorzSqlDB.unique_constraint_errorbs r%idxcftj|jj|S)z4Return a PyPika Parameter object for the given index)pypika ParameterrLformat)r!rWs r"paramz SqlDB.paramis' 5 5 7 > >s CDDr% seq_id_bytesct|tr|St|dk(rtj|dSt|dk(rtj|dSt dt|)z Decode a byte array into a SeqIDbigzUnknown SeqID type with length ) isinstanceintlen from_bytes ValueError)r]s r" decode_seq_idzSqlDB.decode_seq_idmsi lC (  |  !>>,6 6  " $>>,6 6>sQRS Sr%seq_idc|jdkrtj|ddS|jdkrtj|ddStd|)z Encode a SeqID into a byte array@r_r`razUnsupported SeqID: ) bit_lengthrcto_bytesrf)rhs r" encode_seq_idzSqlDB.encode_seq_idzs_    " $<<51 1    C '<<E2 226(;< z)ParameterValue.get_sql..s"$S7aX%7%7%>%>q%A7s)+())rbrQlisttupleryvaluesextendr generatorrdjoinappendrzr[nextr4)r!rvindexes placeholdersvals r"get_sqlzParameterValue.get_sqls djj4- 0 OO " "4:: .X//TZZAG99$S7$SSLl^1%C 3x OO " "4:: .$$++D1C1C,DEC3xr%N) r0r1r2r3rrErr4rrr%r"rtrts5 c    r%rtqueryrzr.cgt_tdt_|t_|j }t tj}||fS)af 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. )ryrrrrzrr)rrzrrs r"rrsCNHOqH"H --/C 8?? #F ;r%)?)+typingrrrrrrtypesr typing_extensionsr r r abcr r threadingr overridesrrrYpypika.querieschromadb.configrrrMr itertoolsrrchromadb.typesrrr6rAryrZrtqueries QueryBuilderr4rrr%r"rs>>55#0 -#  X * % ,H=IH=V 7V%%2:=, >> & &,36, 3c3h  ,r%