Talk:Block nested loop

Untitled

This is referenced in the main SQL article.

is block hashing optional?

it's unclear if "block nested loop" always uses block hashing. sources show conflicting evidence

a mariadb article identifies "block nested loop" and "block hash join" as distinct, separate algorithms https://mariadb.com/kb/en/block-based-join-algorithms/

a highly cited research paper "join algorithm costs revisited" specifies blocks are hashed "We assume that the memory based part of the join is based on hashing" https://citeseerx.ist.psu.edu/document?repid=rep1&type=pdf&doi=733b1e7c0a4d1f12188008e6e6eaa4cb40fd732d

a mysql article on "block nested loop" doesn't mention hashing https://dev.mysql.com/doc/refman/8.4/en/bnl-bka-optimization.html#bnl-optimization

what do you think? Neilc, TiMike is block hashing optional or mandatory in block nested loops? in theory and in practice

Asaf Spiegler (talk) 16:09, 3 December 2024 (UTC)[reply]

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.