1cfd3bbb56
Topic_CSS/Topic_HTML/Topic_JavaScript/Topic_Prompt/Topic_Comfyui 등 기존 카테고리 폴더를 정리하고, Topic_Graphic/Dev 등 신규 산출물과 Topics 내부 세션/메모리 기록을 동기화.
3.1 KiB
3.1 KiB
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
| 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 | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| python-mysql-delete | Python MySQL Delete | Programming_Language | draft | conceptual |
|
B | 0.9 | 2026-07-04 | 2026-07-04 |
|
|
Python MySQL Delete
🎯 한 줄 통찰 (One-line insight)
Just like INSERT, a DELETE needs mydb.commit() to actually take effect, and omitting the WHERE clause deletes every row — the same two warnings from raw SQL DELETE apply identically through the Python connector. [S1]
🧠 핵심 개념 (Core concepts)
DELETE FROM ... WHERE ...— deletes matching records. [S1]mydb.commit()— required for the delete to persist. [S1]- Missing WHERE = delete everything — same risk as raw SQL DELETE. [S1]
mycursor.rowcount— number of rows deleted. [S1]- SQL injection prevention — use
%splaceholders for user-provided delete criteria. [S1]
📖 세부 내용 (Details)
- Basic delete:
sql = "DELETE FROM customers WHERE address = 'Mountain 21'"; mycursor.execute(sql); mydb.commit(); print(mycursor.rowcount, "record(s) deleted"). [S1] - Parameterized delete:
sql = "DELETE FROM customers WHERE address = %s"; adr = ("Yellow Garden 2",); mycursor.execute(sql, adr); mydb.commit(). [S1]
⚖️ 모순 및 업데이트 (Contradictions & updates)
소스에서 모순되는 정보는 발견되지 않음. WHERE 누락 시 전체 삭제된다는 경고가 SQL Delete 챕터와 동일하게 반복됨. [S1]
🛠️ 적용 사례 (Applied in summary)
현재 발견된 실제 적용 사례가 없습니다 — SQL Delete 챕터의 규칙(WHERE 필수, commit 필요)이 mysql.connector API로 그대로 이어진다. [S1]
💻 코드 패턴 (Code patterns)
Parameterized delete with commit (Python):
sql = "DELETE FROM customers WHERE address = %s"
adr = ("Yellow Garden 2", )
mycursor.execute(sql, adr)
mydb.commit()
print(mycursor.rowcount, "record(s) deleted")
✅ 검증 상태 및 신뢰도
- 상태: draft
- 검증 단계: conceptual
- 출처 신뢰도: B (W3Schools — widely used educational reference, not a primary standards body)
- 신뢰 점수: 0.90
- 중복 검사 결과: 신규 생성 (New discovery)
🔗 지식 그래프 (Knowledge Graph)
- 상위/루트: Python Tutorial
- 관련 개념: SQL Delete, Python MySQL Insert, Python MySQL Update
- 참조 맥락: SQL Delete의 위험성(WHERE 누락)이 mysql.connector에서도 동일하게 적용된다.
📚 출처 (Sources)
- [S1] W3Schools — Python MySQL Delete From By — https://www.w3schools.com/python/python_mysql_delete.asp
📝 변경 이력 (Change history)
- 2026-07-04: Initial draft synthesized from the W3Schools "Python MySQL Delete" page (Astra wiki-curation, P-Reinforce v3.1 format).