sorm/README.md

69 lines
2.9 KiB
Markdown
Raw Normal View History

2024-11-22 13:45:03 +00:00
# SORM
## Description
2024-11-22 13:45:03 +00:00
SORM stands for SQL ORM. I made this because I have a love/hate relationship with both. I combined them together to have the best of both worlds!
2024-11-22 13:45:03 +00:00
2024-11-22 13:45:03 +00:00
The naming of my functions and variables are something to get used to. They are all abbreviations, kinda like C stdlib style. It looks weird, but you get used to it quickly and in reality, you just use a few of them.
2024-11-22 13:45:03 +00:00
Examples of common used functions are:
2024-11-22 13:45:03 +00:00
- `sormc(char *path)` connect to database. Returns `int`.
- `sormq(int conn, char *sql, ...)` execute query. Variadic arguments. Works like `printf`. Returns result in CSV format in case of `SELECT`.
2024-11-22 13:45:03 +00:00
- `sorm_csvd(char *csv_data)` dumps your CSV result data to a nice fixed content width table in the terminal.
2024-11-22 13:51:55 +00:00
## CAUTION
This project won't compile on your local PC because `rlib.h` is missing. This is my bundle of libraries that I regularely use. I will add this later as 3rd party lib. Maybe I will cherry pick only the functions that SORM uses out of it to keep the source clean, else I will have thousands of lines nothing to do with this project in the source.
2024-11-22 13:45:03 +00:00
## Thread safety
I wonder if I have configured sqlite3 the right way for thread safety. It maybe requires a manual compilation of the shared object file. Will look into that. SORM is written with thread safety in mind.
## Design choices
2024-11-22 13:45:03 +00:00
I use mainly native types and not custom structs. For example, the db parameter is an int. This is so it can easily communicate with other languages using a shared object file.
2024-11-22 13:45:03 +00:00
Same argument is for the result set of `sormq` (the query function) resulting in a `char *` containing CSV data.
While the performance is nice, it's not written with performance in mind at all.
## Python support
2024-11-22 13:45:03 +00:00
The Python library is low quality. I made it just for fun and test. This is not a defitive version. But it show very well how to communicate with a shared object file. I'm sure someone will be happy with examples how to use variadic functions trough Python to C. See `sorm.py`
2024-11-22 13:45:03 +00:00
## C API examples:
### Connecting
2024-11-22 13:45:03 +00:00
```c
2024-11-22 13:45:03 +00:00
int db = sormc("db.sqlite3");
```
### Create table
2024-11-22 13:45:03 +00:00
This one should return true if executed.
2024-11-22 13:45:03 +00:00
```c
2024-11-22 13:45:03 +00:00
sormq(db, "CREATE TABLE IF NOT EXISTS pony (id INTEGER PRIMARY KEY AUTOINCREMENT,name,age);",NULL);
```
### Inserting
2024-11-22 13:45:03 +00:00
```c
2024-11-22 13:45:03 +00:00
sorm_pk iid = sormq(db, "INSERT INTO pony (id, name, age) VALUES (NULL, %s, %d);",
"Retoorded retoor",
42
);
```
Using `?` is also possible for arguments like this (comfy for Python usage):
2024-11-22 13:45:03 +00:00
```c
2024-11-22 13:45:03 +00:00
sorm_pk iid = sormq(db, "INSERT INTO pony (id, name, age) VALUES (NULL, ?s, ?d);",
"Retoorded retoor",
42
);
```
### Selecting
IN query
2024-11-22 13:45:03 +00:00
```c
2024-11-22 13:45:03 +00:00
sorm_str csv = sormq(db, "SELECT * FROM pony WHERE id in (?d,?d,?d)",1,2,3);
free(sorm_str);
```
LIKE query
2024-11-22 13:45:03 +00:00
```c
2024-11-22 13:45:03 +00:00
sorm_str csv2 = sormq(db, "SELECT * FROM pony WHERE id > %d and age = %d AND name LIKE ?s", 1, 34, "%toor%"));
free(sorm_str);
```
Yes, you did see that right, you can use the default native free!
### Disconnecting
2024-11-22 13:45:03 +00:00
```c
2024-11-22 13:45:03 +00:00
sormd(db);
```