On my previous commit I added a not null constraint for name column on site_nodes, the problem is that main site node on oracle has a NULL name ( given the fact that empty strings are managed as NULL on Oracle ) therefore doesnt make sense to have such constraint.
- Avoiding usage of coalesce function on site_nodes table columns in WHERE clause, this was leading to usage of sequencial scans which can be expensive when having a huge amount of site_nodes. Instead we go for isolation of the case when requestion a node with a null parent ( this would be the main site node ) and we use the = operator so the planner goes for a index scan.- Adding not null constraint to site_nodes(name)
