A safe, extensible ORM and Query Builder for Rust – For feature requests and longer questions also see https://github.com/diesel-rs/diesel/discussions/categories/q-a
That shouldn't mean that this wouldn't be something that can be useful for anyone. I'm just not sure if this should be really part of diesel itself, or should there be some kind of "high-level" crate that uses diesel internally and provides an interface that matches more classical ORM 's. If someone steps up to write such an crate I would definitively try to over some advice and help for implementation there.
I think you doesn't need that much macros for such a project. More likely that you need to define a whole lot of traits and write some generic code + maybe one or two "simple" derive macros (but they are really simple, just take some rust code and generate some rust code, that's not any more complex than writing normal rust code)
I think the more complex part is to decide how the "public" API of such a crate should look like and how to avoid common ORM problems like N+1 queries in such an API.
I think @pksunkara Is working on something like that as well, so maybe you could ask them on their approach and join forces there?
I think maybe for something like this rather that relying on a full blown query hierarchy it be better to just add a derive that builds a players::table.select((players.uid, players.name)) that the end user could simply just use the rest of regular diesel along with it
so you could do
PGPlayerWithID::select() and the rest would be regular diesel commands
PGPlayerWithID::select() and the rest would be regular diesel commands
For that see #2367. As written before: It's not a priority for myself, but I would be happy to accept a complete PR there.
I think maybe for something like this rather that relying on a full blown query hierarchy it be better to just add a derive that builds a players::table.select((players.uid, players.name)) that the end user could simply just use the rest of regular diesel along with it
I have actually finished implementing support for the above in my ORM lib (on top of diesel) using rust macros. I am currently working on solving this issue for INSERT and UPDATE. And then will move on to associations (I have a vague idea on how to solve the n+1 problem)
It uses diesel master
An example on how it is used in a web app, https://github.com/pksunkara/reign/blob/master/examples/full/src/controllers/articles.rs
1 reply
It seems like a bug that you can use
[u8; 8] in a derive Queryable struct but not a derive Insertable struct (you get an error about it not implementing Expression for the latter). I've worked around it with a serialize_as wrapper for now. Should I file a github issue or is there an underlying cause here I haven't thought about?
With diesel features=["postgres"] :
#[macro_use]
extern crate diesel;
table! {
examples (id) {
id -> Int4,
bytes -> Bytea,
}
}
// Compiles
#[derive(Queryable)]
struct Example {
id: i32,
bytes: [u8; 8],
}
// Doesn't compile
#[derive(Insertable)]
#[table_name = "examples"]
struct NewExample {
bytes: [u8; 8],
}
let me look at an example without postgres..
thanks
for now, my code looks like:
table
.filter(available.eq(query.available()))
.limit(query.limit())
.offset(query.offset());diesel is AWESOME~~~
@tzsword I have actually been looking into this issue last week. The issue is that diesel uses some derive macros inside it non proc macros which is why re-exporting doesn't work. I am planning to solve it soon.
Awesomeeeeeeeeeeeeee this is very cool, can I help? I'm a rookie~~
@tzsword You can try to take a stab at it. I am currently a little busy with other stuff. In the file, https://github.com/diesel-rs/diesel/blob/master/diesel/src/macros/mod.rs, we need to remove all
$crate::query_builder::QueryId by adding the derived code locally
Just 10 mins work :D