Currently if you try to archive any object that is versioned you will get a fatal error using PostgreSQL - it doesn't support the multi table delete syntax built using DBQueryBuilder. This can be relatively easily addressed by overloading buildDeleteQuery in PostgreSQLQueryBuilder - the syntax can be changed to use sub-select conditions or CTEs.
Perhaps this issue would be better placed in framework as you might argue that the ORM should generate more SQL engine agnostic queries.
I was in two minds about whether this was type/bug or type/enhancement - It's pretty broken right now but there's a comment in the ORM code saying:
Note that some schemas don't support multiple table deletion
Currently if you try to archive any object that is versioned you will get a fatal error using PostgreSQL - it doesn't support the multi table delete syntax built using
DBQueryBuilder
. This can be relatively easily addressed by overloadingbuildDeleteQuery
inPostgreSQLQueryBuilder
- the syntax can be changed to use sub-select conditions or CTEs.Perhaps this issue would be better placed in framework as you might argue that the ORM should generate more SQL engine agnostic queries.
I was in two minds about whether this was
type/bug
ortype/enhancement
- It's pretty broken right now but there's a comment in the ORM code saying: