1.2.0 — a script can see more of what happened
Added: a write can report the rows it affected. End a statement with and store affected rows in {_rows}: 0 means it ran and matched nothing, while an unset variable means no statement answered — which is what makes a read-check-write safe without a transaction.
Changed: every statement now waits for its work, so the next line reads what the previous one wrote and a failure the database reported always reaches last database error. and wait is still accepted and does nothing, so no existing script has to change.
Fixed: a failure the database reports now really ends its transaction; a whole number that does not fit its column is refused instead of stored as a different number (5000000000 no longer becomes 705032704); MySQL's insert if absent no longer swallows errors other than a duplicate key; a refused read clears its result variable.
Download: https://github.com/heyhey123-git/skript-orm/releases/tag/v1.2.0

adds MongoDB, SQLite, PostgreSQL support:
write database "MongoDB" and the statements, types and limits behave the way they already do on MySQL. SQLite is documented as reachable through the generic "JDBC" type, PostgreSQL's tinyint columns read back as they should, and the jar no longer carries a database driver — Paper downloads the ones a bundled implementation needs on the server's first start.