Files

T

Antigravity Agent c24165b8bc refactor(topics): 멀티 에이전트용 지식 재편 — _Common(공통 기본기) + Domain_* 구조

에이전트 8종(대화형/프로그래머 C·S/디자이너/설계자/기획자/QA/PD/PM)에게
[공통 기본 능력 + 롤별 Specialty] 2층으로 지식을 주입하기 위한 재분류.
문서 내용·포맷은 무수정, 폴더 이동만 (6,372개 문서 수 보존 확인).

- Topic_Programming → Domain_Programming (내부 구조 보존)
- Topic_Graphic → Domain_Design
- Topic_Business → Domain_Product
- Topic_General → Domain_General
- _Common 신설: Math(구 Topic_Math_Specialty), Reasoning(구 General/From_Thinking & Reasoning),
  Reasoning_Creativity(구 General/From_창의성), Communication(Poetic_Blog_Writing + From_writing)
- 타 도메인의 From_* 폴더는 유지 (출처 표기일 뿐, 이미 도메인에 맞게 분류된 문서)
- 빈 폴더 정리 (memory/procedures)
- 에이전트→폴더 매핑은 workspace의 .astra/agent-knowledge-map.json (9개 에이전트)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-11 11:05:56 +09:00

3.3 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

SQL Joins

🎯 한 줄 통찰 (One-line insight)

JOIN combines rows from two or more tables based on a related column between them, with four variants (INNER/LEFT/RIGHT/FULL) differing in which unmatched rows they keep. [S1]

🧠 핵심 개념 (Core concepts)

JOIN clause — combines rows from two or more tables based on a related column. [S1]
(INNER) JOIN — returns only rows with matching values in both tables. [S1]
LEFT (OUTER) JOIN — returns all rows from the left table, plus matched rows from the right table. [S1]
RIGHT (OUTER) JOIN — returns all rows from the right table, plus matched rows from the left table. [S1]
FULL (OUTER) JOIN — returns all rows when there is a match in either table. [S1]

🧩 추출된 패턴 (Extracted patterns)

Related-column identification — before writing a JOIN, identify the shared column between two tables (e.g. CustomerID appears in both "Orders" and "Customers"). [S1]

📖 세부 내용 (Details)

Example relationship: the "Orders" table's CustomerID refers to the "Customers" table's CustomerID. [S1]
INNER JOIN combining the two: SELECT Orders.OrderID, Customers.CustomerName, Orders.OrderDate FROM Orders INNER JOIN Customers ON Orders.CustomerID=Customers.CustomerID;. [S1]
The four JOIN types are summarized as covering: matches-only (INNER), left-preserving (LEFT), right-preserving (RIGHT), and both-preserving (FULL). [S1]

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

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

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — 이 문서는 개론이며, 각 JOIN 유형은 이어지는 개별 챕터(Inner/Left/Right/Full/Self Join)에서 상세히 다뤄진다. [S1]

💻 코드 패턴 (Code patterns)

Basic INNER JOIN (SQL):

SELECT Orders.OrderID, Customers.CustomerName, Orders.OrderDate
FROM Orders
INNER JOIN Customers ON Orders.CustomerID=Customers.CustomerID;

✅ 검증 상태 및 신뢰도

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

🔗 지식 그래프 (Knowledge Graph)

상위/루트: SQL Tutorial
관련 개념: SQL Inner Join, SQL Left Join, SQL Right Join, SQL Full Join, SQL Aliases
참조 맥락: JOIN 계열 챕터 전체의 개론 — 이후 4가지 JOIN 유형이 각각 별도 문서로 심화된다.

📚 출처 (Sources)

[S1] W3Schools — SQL Joins — https://www.w3schools.com/sql/sql_join.asp

📝 변경 이력 (Change history)

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

3.3 KiB Raw Blame History