sqlalchemy-declarative-extensions
sqlalchemy-declarative-extensions copied to clipboard
DanCardin
Library to declare additional kinds of objects not natively supported by SqlAlchemy/Alembic.
It would be nice to have the possibility to provide the `WITH NO DATA` directive as a keyword argument to the @view decorator from sqlalchemy_declarative_extensions. Because right now, we have...
It would be nice to have the possibility to provide the `SECURITY DEFINER` directive as a field to the sqlalchemy_declarative_extensions.dialects.postgresql.Function, along with `language` or `returns` fields. Because right now, we...
Add posibility to manage PostgreSQL **procedures** in addition to **functions**. Something like this: ```python refresh_my_view_procedure = Procedure( "refresh_my_view", """ BEGIN REFRESH MATERIALIZED VIEW my_view WITH DATA; END """, language="plpgsql", )...
Fixes https://github.com/DanCardin/sqlalchemy-declarative-extensions/issues/59
Refactors out the notion of dialect-specific view classes that can contain dialect-specific view behaviors. This moves the handling of PGView and PGMaterializedView adapters from alembic_utils to that postgres dialect definition....
This implies all "ops" should implement a `to_diff_tuple` which accepts no arguments and roughly is able to return the raw sql it should generate. The two problems here are: *...
Resolves https://github.com/DanCardin/sqlalchemy-declarative-extensions/issues/103 This PR adds support for declaring `Function`s with `parameters` for both the MySQL and the PostgreSQL dialects. The PostgreSQL dialect of `Function`s now also support a new `volatility`...
