Julius de Bruijn

This whole issue is on hold now due to not having time in any team and if we merge this, we'll break our main product (it needs to get the...

Yeah. I was hit by the same problem once, and what I found out it would be nice if that function returns a `Function` type directly. How you can do...

https://docs.rs/quaint/0.2.0-alpha.9/quaint/ast/struct.Function.html

Also some examples would be super cool before we kick the 0.2 out from the door. Ping @tomhoule let's do that soon :)

In the version `v0.2.0-alpha.11` the function interfaces to all but the `row_number` are a bit easier: ```rust .value(aggregate_to_string(("role", "display"))).alias("assigned_roles") ``` ... should work.

The problem is the `Aliasable` trait that is mainly implemented for the `Table` and the `&str/(&str, &str)` etc. that will turn into `Table`. This would clash with `Column`, and I...

Also in your example: ``` rust .column(Column::from(("employee", "id"))) .column(Column::from(("employee", "created"))) .column(Column::from(("employee", "updated"))) .column(Column::from(("employee", "deleted"))) .column(Column::from(("employee", "casino_id"))) .column(Column::from(("employee", "uuid"))) .column(Column::from(("employee", "name_first"))) .column(Column::from(("employee", "name_last"))) .column(Column::from(("employee", "title"))) ``` can be written (if not...

Hmm, I'll take a look later today.

@scull7 There's a PR that should solve your problem here: https://github.com/prisma/quaint/pull/123/files The type inference here can be tricky, so what you can do with this PR is either: ``` rust...

We have plans to release 0.2 #soon. ;) What is still missing from it: Microsoft SQL Server support. That should be ready around mid-May.