Hello,
this project looks very interesting, but there are two features at the moment which prevent my migration from sqlalchemy to it:
- Composite primary keys -- in sqlalchemy you can set
primary_key=True on multiple fields, making their combination the primary key of the table, whereas in oxyde it appears only single column can be selected as such
- Support for subqueries -- in sqlalchemy you can
select(...).where(...).subquery() and then use that eg in a .join(...), converting the full thing to a single sql query
I apologize in advance if my assessment of existing Oxyde features is incorrect, I did only a brief skim.
Hello,
this project looks very interesting, but there are two features at the moment which prevent my migration from sqlalchemy to it:
primary_key=Trueon multiple fields, making their combination the primary key of the table, whereas in oxyde it appears only single column can be selected as suchselect(...).where(...).subquery()and then use that eg in a.join(...), converting the full thing to a single sql queryI apologize in advance if my assessment of existing Oxyde features is incorrect, I did only a brief skim.