Search Results
                    
                    
            https://dev.mysql.com/doc/x-devapi-userguide-shell-js/en/working-with-locking.html
                                This section describes how to use the lockShared() and lockExclusive() methods for both the Collection.find() and Table.select() methods. Both locking methods support the NOWAIT and SKIP LOCKED InnoDB locking modes.  X DevAPI supports MySQL locking ...
                                            
                https://dev.mysql.com/doc/x-devapi-userguide-shell-python/en/devapi-users-working-with-relational-tables-and-documents.html
                                 After seeing how to work with documents and how to work with relational tables, this section explains how to combine the two and work with both at the same time. This way the advantages of both documents and relational tables can be combined. It ...
                                            
                https://dev.mysql.com/doc/x-devapi-userguide-shell-python/en/working-with-locking.html
                                This section describes how to use the lockShared() and lockExclusive() methods for both the Collection.find() and Table.select() methods. Both locking methods support the NOWAIT and SKIP LOCKED InnoDB locking modes.  X DevAPI supports MySQL locking ...
                                            
                https://dev.mysql.com/doc/heatwave/en/mys-hw-auto-unload-syntax.html
                                This adds an include list to exactly specify the tables to unload, which eliminates the need to include a database and exclude unnecessary tables. mysql> CALL sys.HEATWAVE_UNLOAD_all ([options]); options: { JSON_OBJECT("key","value"[,"key","value"] ...
                                            
                https://dev.mysql.com/doc/heatwave/en/mys-hw-genai-run-chat.html
                                And, it uses both the language specified for generating the output and the name of the embedding model used to embed the input query to find relevant tables containing information in the same language and vector embeddings from the sameembedding ...
                                            
                https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-auto-loading-data-par.html
                                The escape character is the backslash character, and it is a reserved character in both JSON and MySQL. Therefore, it is necessary to escape the backslash character twice, and specify \\ for both JSON and MySQL.  Review the following examples to see ...
                                            
                https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-auto-loading-data-rp.html
                                The escape character is the backslash character, and it is a reserved character in both JSON and MySQL. Therefore, it is necessary to escape the backslash character twice, and specify \\ for both JSON and MySQL.  Review the following examples to see ...
                                            
                https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-loading-data-par.html
                                Note When creating the table with JSON syntax, the escape character is the backslash character, and it is a reserved character in both JSON and MySQL. Therefore, it is necessary to escape the backslash character twice, and specify \\ for both JSON ... Review the following examples to see the different ways to use pre-authenticated requests (PAR) to specify files when creating external tables ...
                                            
                https://dev.mysql.com/doc/heatwave/en/mys-hw-lakehouse-loading-data-resource-principal.html
                                The escape character is the backslash character, and it is a reserved character in both JSON and MySQL. Therefore, it is necessary to escape the backslash character twice, and specify \\ for both JSON and MySQL.  Review the following examples to see ...
                                            
                https://dev.mysql.com/doc/heatwave/en/mys-hw-partitioning.html
                                If both values are 1 (i.e., "prepart": [1, 1]), then data placement partitions is not used both the branches.  When data is loaded into MySQL HeatWave, it is partitioned by the table primary key and sliced horizontally for distribution among MySQL ...