Goran

ATM we can do it for `insert`, `update` and `delete` queries by doing following: ```rust let caching_session: CachingSession; let res = model.insert().trace(true).execute(caching_session).await?; if let Some(tracing_id) = res.tracing_id { let info...

Additionally, in case of error you can also cover `read` query by printing `CharybdisError` as it always print static query that is generated at compile time, however it does not...

I would recommend the following syntax: ```rust #[charybdis_model( table_name = users, partition_keys = [id], clustering_keys = [], )] pub struct User { id: Uuid, username: Uuid, #[charybdis(writetime = "username")] username_wt:...

I am quite busy these few weeks. I will probably just do small updates and fixes until mid-July.

Resolved in [v0.7.8](https://github.com/nodecosmos/charybdis/releases/tag/v0.7.8)

Not planning it ATM, I'll assign myself when I get a chance. Meanwhile, PR is welcomed. `insert_using_ttl(seconds: u32)` and `update_using_ttl(seconds: u32)` are good.

TTL in scylla query is specified in seconds so I thought it's just easier. However, you are right, we could have duration and convert it in seconds within method.

> It would be easier to wrap it and bring to other drivers. Not sure if it will be possible as `USING TTL` is part of the query itself.

In Charybdis we make use of `partial_` to update partial fields. In our app we usually have partial model for each action e.g. Lets say we have model user: ```rust...

Well, we don't support that ATM. In our platform we have endpoint for each set of fields that we want to update at once, and we know them in advance....