njord-rs / njord Goto Github PK

Instead of getting back:

Result<Vec<HashMap<String, Value>>>

Getting something similar to:

Result<Vec<Table>>

Would be great if we could add features like below to not need to include the njord_derive in the dependencies list:

njord = { version = "0.1.0", features = ["derive"] }

We need to have method chaining for SELECT since we can have multiple conditions. An example of a use case would be:

sqlite::select(columns).from(table).where(condition);

https://rust-lang.github.io/mdBook/guide/creating.html

We need to be able to fix the possibility of storing a vector of structs that derive the Table procedural macro:

#[derive(Table)]
#[table_name = "orders"]
pub struct Order {
    id: usize,
    user: User,             // one-to-one relationship
    products: Vec<Product>, // one-to-many relationship - populates from based on junction table (gets from macro attribute "table_name" and combines them for example, orders_products)
    total_cost: f64,
}

As you can see here when we define a field called products and add a vector of Product. It will complain about:

- doesn't satisfy `syn::Type: ToString` or `syn::Type: std::fmt::Display`

We need to be able to support this in the njord_derive library.

We need to update the procedural derive macro to make all fields possible to use Option<T> if we for example have set the table definition for allowing NULL. If no Option is set, it's automatically NOT NULL.

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

We need to implement in the procedural macro so that id fields can be used with Option<T> since we want the user to control if they want to populate the id field when doing an INSERT operation. If you want SQlite to handle autoincrement itself, we don't need to add a value to it.

Commands that should exist:

njord migration generate <name>
njord migration run
njord migration rollback

Flags that should exist on njord:

• -v and --version
• -h and --help

Flags that should exist on njord migration:

• --dry-run (simulate the migration)
• --env (specify development/test/staging/production etc)
• --dir (specify target directory for generated migration changes)
• --to (rollback to specific version, for example 20191225120000)
• --log-level (standard, debug etc)

Examples:

njord setup
njord migration generate <name> --env=development --dry-run
njord migration run --env=production --log-level=debug
njord migration rollback --env=development --to=20191225120000

We want to add the possibility to add junction tables for a MANY-TO-MANY relationship if we define our tables such as:

#[derive(Table, Default)]
struct Posts {
    title: String,
    description: String,
    category: Categories
}

#[derive(Table, Default)]
struct Categories {
    name: String,
}

Would be nice that we can activate features with what database support is needed like this:

njord = { version = "0.1.0", features = ["derive", "sqlite", "mysql", "postgres"] }