Menú
Use when writing INSERT, UPDATE, DELETE, or conflict-handling queries with knex_dart.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when configuring connection pools, executing raw SQL, or tapping observability streams on knex_dart driver clients.
Use when choosing between SQL-only knex_dart usage and a live driver package, or when writing the first connected query.
Use when instrumenting knex_dart live driver wrappers with OpenTelemetry spans, DB client duration metrics, hooks, transactions, or stream/query interceptor behavior.
Use when generating SQL with knex_dart query builders: filtering, joins, grouping, CTEs, unions, and SQL inspection.
Use when defining database migrations with knex_dart's Migrator — code-first, SQL-directory, or schema-input styles.
Use when creating tables, altering schema, or running atomic write flows with knex_dart driver wrappers.
| name | knex-mutations |
| description | Use when writing INSERT, UPDATE, DELETE, or conflict-handling queries with knex_dart. |
| metadata | {"knex_dart_version":"1.2.1"} |
This skill covers write operations. Use KnexQuery.forDialect(...) for compile-only examples, and a driver wrapper (KnexPostgres, KnexSQLite, etc.) when you need to execute against a real database.
final q = KnexQuery.forDialect(KnexDialect.postgres);
// Single row
final insert1 = q
.from('users')
.insert({'name': 'Alice', 'email': 'alice@example.com'})
.toSQL();
// Bulk insert
final insert2 = q
.from('users')
.insert([
{'name': 'Alice', 'email': 'alice@example.com'},
{'name': 'Bob', 'email': 'bob@example.com'},
])
.toSQL();
// RETURNING (PostgreSQL and SQLite only)
final insert3 = q
.from('users')
.insert({'name': 'Alice'})
.returning(['id', 'name'])
.toSQL();
Chain .onConflict(...) immediately after .insert(...).
// Do nothing on conflict
final upsert1 = q
.from('users')
.insert({'email': 'alice@example.com', 'name': 'Alice'})
.onConflict('email')
.ignore()
.toSQL();
// Upsert — update all non-conflict columns
final upsert2 = q
.from('users')
.insert({'email': 'alice@example.com', 'name': 'Alice'})
.onConflict('email')
.merge()
.toSQL();
// Upsert — update specific columns only
final upsert3 = q
.from('users')
.insert({'email': 'alice@example.com', 'name': 'Alice'})
.onConflict('email')
.merge(['name'])
.toSQL();
// Composite conflict target
final upsert4 = q
.from('event_attendees')
.insert({'event_id': 1, 'user_id': 42})
.onConflict(['event_id', 'user_id'])
.ignore()
.toSQL();
Always add a .where(...) clause unless you intend to update every row.
final update = q
.from('users')
.where('id', '=', 1)
.update({'name': 'Alicia', 'updated_at': DateTime.now().toIso8601String()})
.toSQL();
// UPDATE … RETURNING (PostgreSQL / SQLite)
final updateReturning = q
.from('users')
.where('active', '=', false)
.update({'active': true})
.returning(['id'])
.toSQL();
final delete = q
.from('users')
.where('id', '=', 1)
.delete()
.toSQL();
// DELETE … RETURNING (PostgreSQL / SQLite)
final deleteReturning = q
.from('sessions')
.where('expired_at', '<', DateTime.now().toIso8601String())
.delete()
.returning(['id', 'user_id'])
.toSQL();
final inc = q
.from('posts')
.where('id', '=', 1)
.increment('views')
.toSQL(); // UPDATE posts SET views = views + 1 WHERE id = ?
final dec = q
.from('inventory')
.where('product_id', '=', 99)
.decrement('stock', 5)
.toSQL(); // UPDATE inventory SET stock = stock - 5 WHERE product_id = ?
Driver wrappers expose dedicated methods that return List<Map<String, dynamic>> (RETURNING rows or an empty list).
import 'package:knex_dart_postgres/knex_dart_postgres.dart';
final db = await KnexPostgres.connect(
host: 'localhost', port: 5432,
database: 'myapp', username: 'user', password: 'pass',
);
// Insert and retrieve returned id
final rows = await db.insert(
db.queryBuilder()
.table('users')
.insert({'name': 'Alice', 'email': 'alice@example.com'})
.returning(['id']),
);
final newId = rows.first['id'];
// Update
await db.update(
db.queryBuilder()
.table('users')
.where('id', '=', newId)
.update({'name': 'Alicia'}),
);
// Delete
await db.delete(
db.queryBuilder()
.table('users')
.where('id', '=', newId)
.delete(),
);
.returning() is PostgreSQL and SQLite only. Omit it for MySQL, MSSQL, BigQuery..onConflict() requires PostgreSQL (ON CONFLICT) or SQLite (ON CONFLICT clause); not available on MySQL 5.x..where() on an UPDATE or DELETE affects every row — do this intentionally, never accidentally.https://docs.knex.mahawarkartikey.in/raw/query-building/write-operations.mdhttps://docs.knex.mahawarkartikey.in/raw/query-building/schema-builder.md