Open dantleech opened 8 years ago
/cc @symfony-cmf/core
there are also doctrine extensions to make manifest trees on doctrine orm. not sure how much those could be useful instead.
i have nothing against doing these things, but don't see them as a priority for the cmf.
@dbu this isn't about making a tree (i.e. nested set, materialized path) in Doctrine ORM, its about taking an existing Entity and representing it as a resource, using fields as path elements, creating a virtual hierarchy. (though is that what you meant by manfest tree?)
ah, i see. sounds lightweight enough then.
:+1: Except that I would replace property access + sql with Symfony ExpressionLanguage instead:
name: 'model.clientRef ~ '-' ~ model.invoiceNo'
shards: ['year(date)', 'month(date)']
property access + sql with Symfony ExpressionLanguage instead:
Also replace the SQL? Was thinking this would be just DBAL SQL. If we replaced SQL with expression language it would be lots of work I would think.
We could support the Doctrine ORM by using "sharding" based on table fields to provide a hierarchy.
By providing a list of SQL field specifications we should be able to emulate a hierarchy.