Azat Ibrakov

Adding same flags to `RUSTDOCFLAGS` environment variable fixed the issue in my case

~since `__setstate__` requires a mutable reference is there a possibility to have a `pickle` support for a [`#[pyclass(frozen)]` class](https://pyo3.rs/v0.19.0/class.html#frozen-classes-opting-out-of-interior-mutability)?~ never mind, I've switched to `__reduce__` method https://github.com/lycantropos/rithm/blob/765d1990800d47e169f84912b16a9857c0575fff/src/lib.rs#L441-L449

I can see that like: 1. If constraint's `sqltext` field is an SQLAlchemy expression, we can convert it to plaint string based on dialect using statement compiler like ```python dialect.statement_compiler(dialect,...

The short answer is: no, we have no support for constraints yet, and I think generating pseudo-random records for tables with foreign keys will require new function that will handle...

@Mec-iS: unique columns should be supported, that's odd, can you please provide a minimal example to reproduce?

you can always generate a list of records with unique/primary key constraints taken into consideration, but this obviously won't work by default for non-empty tables (and it probably shouldn't) from...

@Mec-iS: please take a look at [second option in the README](https://github.com/lycantropos/hypothesis_sqlalchemy#records): ```python >>> from hypothesis_sqlalchemy import tabular >>> records_lists = tabular.records.lists_factory(user_table, ... min_size=2, ... max_size=5, ... email_address=strategies.emails()) ```

dropping tables is outside of this library's context, but there is [`Table.drop` method](https://docs.sqlalchemy.org/en/latest/core/metadata.html#sqlalchemy.schema.Table.drop)

Thanks for the issue. We are using [`functools.singledispatch`](https://docs.python.org/3/library/functools.html#functools.singledispatch), so there is no way to pass non-type objects to `from_type.register`. But it looks like we can add a special case for...

I'm not sure I understand the problem, can you please provide minimal reproducible example?