AI cocok banget karo konversi format (CSV ↔ JSON ↔ SQL) lan skrip migrasi amarga aturan transformasi iku mekanis. Triknya ya ngasih cukup konteks supaya bisa bener lan aman: skema, baris sampel, lan syarat keamanan sing jelas.
AI cocok banget karo konversi format (CSV ↔ JSON ↔ SQL) lan skrip migrasi amarga aturan transformasi iku mekanis. Triknya ya ngasih cukup konteks supaya bisa bener lan aman: skema, baris sampel, lan syarat keamanan sing jelas.
import csv
# Source CSV: id,email,signup_date (signup_date may be blank)
# Target table: users(id INT, email TEXT NOT NULL, signup_date DATE NULL)
def csv_to_sql(path: str) -> list[str]:
statements = []
with open(path, newline="", encoding="utf-8") as f:
for row in csv.DictReader(f):
email = row["email"].strip()
if not email: # validate: skip invalid rows, don't insert garbage
continue
date = row["signup_date"].strip() or None
email_sql = email.replace("'", "''") # escape quotes to avoid broken SQL / injection
date_sql = f"'{date}'" if date else "NULL"
# ON CONFLICT makes it idempotent: re-running won't create duplicates
statements.append(
f"INSERT INTO users (id, email, signup_date) "
f"VALUES ({int(row['id'])}, '{email_sql}', {date_sql}) "
f"ON CONFLICT (id) DO NOTHING;"
)
return statements
Komentare nandai bagean sing penting: validasi (lirwakne email kosong), escaping (tanda kutip), lan idempotency (ON CONFLICT DO NOTHING). Minta AI kanggo kalebu kabéh telu — iku bab-bab sing skrip naif biyen lali.
Migrasi data iku risiko tinggi lan asring mung sapisan: skrip sing dobel-usap utawa busak baris bisa larang-larange kanggo dibatalke. AI nyepet-nyepetne nulis konversi, nanging properti keamanan — idempotence, validasi, lan dry-run ing salinan — ora bisa ditawar. Nggegani skrip sing dibuat minangka draf sing kudu kakowe lan ditesting, ora minangka apa-apa sing kudu lumaku wuta marang data nyata.