Files

T

Antigravity Agent e9cbf23ab5 docs(10_Wiki): Dev 폴더 누락분 반영 — Topic_Programming으로 통합

이전 재구성 작업에서 Dev/ 폴더가 누락되었던 것을 반영.

- Dev/Topic_Programming(중첩 폴더, 78개)은 Dev 자체 최상위 폴더들
  (Architecture/Conventions/Engineering_Intelligence 등)과 완전 중복이라 제거.
- Dev 최상위 엔지니어링 지식 폴더(Architecture/Conventions/Engineering_Intelligence/
  Failure_Library/Generalized_Principles/Language/Pattern_Catalog/Platform_Guides/
  Subsystems, 77개)는 이미 Topic_Programming/Topic_Programming에 더 최신 버전이
  존재해 중복 제거(고유 콘텐츠 1개는 예외 처리하여 이동 보존).
- Dev의 W3Schools 언어 튜토리얼 폴더(Topic_C/CPP/CSS/CSharp/HOWTO/HTML/Java/
  JavaScript/PHP/Python/SQL/W3CSS, 1201개)는 전부 Topic_Programming 하위로 이동.
- 에이전트 운영 상태(.astra/docs)는 그대로 유지, 콘텐츠 폴더만 정리.
- Topic_Programming 최종 문서 수: 2784 → 3985.

2026-07-05 00:39:13 +09:00

3.6 KiB

Raw Blame History

id, title, category, status, verification_status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, created_at, updated_at, review_reason, merge_history, tags, raw_sources, applied_in, github_commit

title

Python MySQL Join

🎯 한 줄 통찰 (One-line insight)

INNER JOIN silently drops users with no favorite product (Hannah, Michael) — the same rows only reappear if you switch to LEFT JOIN, making the choice of join type directly visible in which rows survive. [S1]

🧠 핵심 개념 (Core concepts)

JOIN via raw SQL — combining users and products tables on users.fav = products.id, executed through the same cursor pattern. [S1]
INNER JOIN (default via JOIN) — only matching rows in both tables; users with no favorite product are excluded. [S1]
LEFT JOIN — keeps ALL users, even those without a matching product (fav is NULL). [S1]
RIGHT JOIN — keeps ALL products, even those no user has favorited. [S1]

🧩 추출된 패턴 (Extracted patterns)

Missing rows are the tell — the source explicitly points out that Hannah and Michael (no favorite product) vanish under INNER/RIGHT JOIN but reappear under LEFT JOIN — a concrete way to verify which join type is actually in effect. [S1]

📖 세부 내용 (Details)

Sample data: users table has fav referencing products.id; some users (Hannah, Michael) have no fav value. [S1]
INNER JOIN: sql = "SELECT users.name AS user, products.name AS favorite FROM users INNER JOIN products ON users.fav = products.id" — excludes users with no favorite. [S1]
LEFT JOIN: same query with LEFT JOIN — includes ALL users, even without a favorite. [S1]
RIGHT JOIN: same query with RIGHT JOIN — includes ALL products, even unfavorited ones; still excludes favorite-less users. [S1]

⚖️ 모순 및 업데이트 (Contradictions & updates)

소스에서 모순되는 정보는 발견되지 않음.

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — SQL Inner/Left/Right Join 챕터에서 이미 배운 동작 차이를 실제 mysql.connector 쿼리로 재확인하는 문서다. [S1]

💻 코드 패턴 (Code patterns)

LEFT JOIN to include unmatched rows (Python):

sql = "SELECT \
  users.name AS user, \
  products.name AS favorite \
  FROM users \
  LEFT JOIN products ON users.fav = products.id"
mycursor.execute(sql)
myresult = mycursor.fetchall()

✅ 검증 상태 및 신뢰도

상태: draft
검증 단계: conceptual
출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
신뢰 점수: 0.90
중복 검사 결과: 신규 생성 (New discovery)

🔗 지식 그래프 (Knowledge Graph)

상위/루트: Python Tutorial
관련 개념: SQL Inner Join, SQL Left Join, SQL Right Join, Python MySQL Select
참조 맥락: SQL JOIN 동작 차이를 mysql.connector로 실증 — 사라지는/나타나는 행으로 join 유형을 검증할 수 있다.

📚 출처 (Sources)

[S1] W3Schools — Python MySQL Join — https://www.w3schools.com/python/python_mysql_join.asp

📝 변경 이력 (Change history)

2026-07-04: Initial draft synthesized from the W3Schools "Python MySQL Join" page (Astra wiki-curation, P-Reinforce v3.1 format).

3.6 KiB Raw Blame History