skript-orm

Addon skript-orm 1.2.0

  • Welcome to skUnity!

    Welcome to skUnity! This is a forum where members of the Skript community can communicate and interact. Skript Resource Creators can post their Resources for all to see and use.

    If you haven't done so already, feel free to join our official Discord server to expand your level of interaction with the community!

    Now, what are you waiting for? Join the community now!

heyhey123

New Member
Nov 11, 2025
6
0
1
heyhey123 submitted a new resource:

skript-orm - An ORM plugin for Skript, aimed at providing a user-friendly & high performance interface for Skript

Markdown (GitHub flavored):
# skript-orm

An ORM for Skript: describe a table once, then read and write rows with Skript syntax instead of
writing SQL.

## What a script looks like

```sk
on load:
    create a connection to database "MySQL" with properties:
        url: "jdbc:mysql://localhost:3306/mydb"
        username: "root"
        password: "123456"

    register a database table "users":
        id: bigint, primary key, auto increment, not null
        name: string(64), not null
        age: int...

Read more about this resource...
 
heyhey123 updated skript-orm with a new update entry:

v1.1.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.

Read the rest of this update entry...
 
heyhey123 updated skript-orm with a new update entry:

v1.2.0

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

Read the rest of this update entry...