Aldjemy integrates SQLAlchemy into an existing Django project, to help you build complex queries that are difficult for the Django ORM.
While other libraries use SQLAlchemy reflection to generate SQLAlchemy models, Aldjemy generates the SQLAlchemy models by introspecting the Django models. This allows you to better control what properties in a table are being accessed.
aldjemy to your
Aldjemy will automatically add an
sa attribute to all models,
which is an SQLAlchemy
Explicit joins are part of the SQLAlchemy philosophy, so don't expect Aldjemy to be a Django ORM drop-in replacement. Instead, you should use Aldjemy to help with special situations.
You can add your own field types to map django types to sqlalchemy ones with
ALDJEMY_DATA_TYPES settings parameter.
Parameter must be a
dict, key is result of
value must be a one arg function. You can get idea from
Also it is possible to extend/override list of supported SQLALCHEMY engines
ALDJEMY_ENGINES settings parameter.
Parameter should be a
dict, key is substring after last dot from
Django database engine setting (e.g.
value is SQLAlchemy driver which will be used for connection (e.g.
It could be helpful if you want to use
Often django models have helper function and properties that helps to represent the model's data (__str__), or represent some model based logic.
To integrate it with aldjemy models you can put these methods into a separate mixin:
class TaskMixin: def __str__(self): return self.code class Task(TaskMixin, models.Model): aldjemy_mixin = TaskMixin code = models.CharField(_('code'), max_length=32, unique=True)
Voilà! You can use
__str__ on aldjemy classes, because this mixin will be
mixed into generated aldjemy model.
If you want to expose all methods and properties without creating a separate mixin class, you can use the aldjemy.meta.AldjemyMeta metaclass:
class Task(models.Model, metaclass=AldjemyMeta): code = models.CharField(_('code'), max_length=32, unique=True) def __str__(self): return self.code
The result is same as with the example above, only you didn't need to create the mixin class at all.
Make a Pull Request with updated changelog and bumped version of the projectpoetry version (major|minor|patch) # choose which version to bump
Once the pull request is merged, create a github release with the same version, on the web console or with github cli.gh release create