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.8 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 Insert

🎯 한 줄 통찰 (One-line insight)

mydb.commit() is not optional — without it, INSERT/executemany() changes silently never reach the table, since the connector buffers writes until explicitly committed. [S1]

🧠 핵심 개념 (Core concepts)

%s placeholders — sql = "INSERT INTO customers (name, address) VALUES (%s, %s)" — parameterized, injection-safe insertion. [S1]
mycursor.execute(sql, val) — executes with a tuple of values bound to the placeholders. [S1]
mydb.commit() — REQUIRED to persist changes; without it, no changes are made to the table. [S1]
mycursor.rowcount — number of rows affected by the last statement. [S1]
executemany(sql, val) — inserts multiple rows at once; val is a list of tuples. [S1]
mycursor.lastrowid — the auto-generated ID of the last inserted row (only the LAST row's ID if multiple were inserted). [S1]

🧩 추출된 패턴 (Extracted patterns)

commit() is the universal write-finalizer — every mutating operation (INSERT/UPDATE/DELETE) in this whole Python-MySQL series requires the same mydb.commit() call, making it the single most important line to remember across all of them. [S1]

📖 세부 내용 (Details)

Single insert with commit: sql = "INSERT INTO customers (name, address) VALUES (%s, %s)"; val = ("John", "Highway 21"); mycursor.execute(sql, val); mydb.commit(); print(mycursor.rowcount, "record inserted."). [S1]
Multiple rows: val = [('Peter','Lowstreet 4'), ...]; mycursor.executemany(sql, val); mydb.commit(). [S1]
Get last inserted ID: print("1 record inserted, ID:", mycursor.lastrowid). [S1]

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

소스에서 모순되는 정보는 발견되지 않음. commit()이 없으면 아무 변경도 반영되지 않는다는 점이 "Important!"로 강조됨. [S1]

🛠️ 적용 사례 (Applied in summary)

현재 발견된 실제 적용 사례가 없습니다 — SQL Injection/Parameters 챕터에서 배운 파라미터화 쿼리(%s)가 여기서 mysql.connector의 실제 구현으로 이어진다. [S1]

💻 코드 패턴 (Code patterns)

Insert with required commit() (Python):

sql = "INSERT INTO customers (name, address) VALUES (%s, %s)"
val = ("John", "Highway 21")
mycursor.execute(sql, val)
mydb.commit()  # required, or no changes persist
print(mycursor.rowcount, "record inserted.")

✅ 검증 상태 및 신뢰도

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

🔗 지식 그래프 (Knowledge Graph)

상위/루트: Python Tutorial
관련 개념: Python MySQL Create Table, SQL Parameters, Python MySQL Update
참조 맥락: commit()이 필요한 모든 쓰기 작업(Insert/Update/Delete)의 공통 패턴 확립.

📚 출처 (Sources)

[S1] W3Schools — Python MySQL Insert Into Table — https://www.w3schools.com/python/python_mysql_insert.asp

📝 변경 이력 (Change history)

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

3.8 KiB Raw Blame History