yūdachi

A workaround is to use cargo workspace: create one crate for MySql, one for Postgres, and third that imports them. So you can have different `DATABASE_URL`s for each one.

@mehcode To be honest, I don't like the idea of using macro here. Because it seems to increase both compile time and build size. Besides, I think a flexible and...

I suggest using sql comment simply because it's extendable. It's is definitely better If we can have a `config!()` macro with optional named parameters like: ```rust config!( DATABASE_URL = "...",...

Thanks for reporting this and apologize for the delay in replying. `#[xml(text)]` doesn't support `Option` now. As a workaround, you can use `Cow` directly, it will fall back to empty...

Sorry for replying late, I was out of town. I rarely use xml namespace feature, so i'm not quite sure about the use case in real world. Could you provide...

Thanks for the pr! But we cannot add `XmlWrite` and `XmlRead` bounds for `T`. Because it's only required for `child` field.

Ok, it's trickier than I thought. We may need to introduce a new trait `XmlReadOwned` for preventing some lifetime issues, just like serde does.

This was implemented by 2ba2a40. Check out [this](https://github.com/PoiScript/strong-xml/blob/master/test-suite/tests/where_clause.rs) for a working example. Closing.

> I thought maybe by saying that the return is valid for 'static if the '__input got zero other lifetimes bound to it? So it would still be one trait?...

just implemented in commit 0b70cf04157ba57d26fbff6c096899ecef7e1e80, but not released yet.