this is to say that just as with math where * comes before + operations, && comes before assignment in this case.
So it's cool you're thinking about this :)
I find it hard to balance, not enough with too much. In the past I tended to go towards over optimization and so now I'm trying not to swing all the way to the other end of the spectrum (no performance optimizations)
Yeah, hence "trick" ;p
The biggest trick with Silverstripe is trying to minimise the number of database trips you make. The ORM makes it so easy to forget about it and flippantly barrage the connection with queries.
@Admonish you have to replace
sql or such (i.e. get the query before calling column).
Save the ORM call to a variable, then you can separately call
column on it.
I bet it's namesp... no wait because how would stage show correct? :s
I would guess at
owns - but that would imply the use of content blocks, etc. which I'm assuming you're not using (otherwise you'd have said)
very odd issue!
all out of ideas, sorry