On 08/09/2010 19:23, Gunnlaugur Briem wrote:
http://communities.bmc.com/communities/docs/DOC-9902
Thanks for all of the references, but this one in particular.
Materialized paths looks like its the closest to what I'm after.
However, with materialized paths, I'm wondering with a structure
On 09/09/2010 02:18 AM, Chris Withers wrote:
On 08/09/2010 19:23, Gunnlaugur Briem wrote:
http://communities.bmc.com/communities/docs/DOC-9902
Thanks for all of the references, but this one in particular.
Materialized paths looks like its the closest to what I'm after.
However, with
Conor wrote:
SELECT EXISTS (SELECT 1 FROM access_control WHERE (path = '/a' OR path LIKE
'/a/%') AND user = :user AND permission = :permission)
Most materialized path queries use LIKE a lot. As long as you keep the %
character at the end, a good DB will be able to use an index to speed up
Hi Chris,
this is more of a relational design question than SQLAlchemy-related,
but take a look at this for an at-a-glance summary of different
approaches and their pros and cons:
http://vadimtropashko.wordpress.com/2008/08/09/one-more-nested-intervals-vs-adjacency-list-comparison/
... here for
