Has something changed in 3.0.2 that would result in a TON more SHOW FULL FIELDS queries?

[Marcus Nyeholt]

I've gone from ~30 queries for a particular page to ~230 - the majority of these are queries like SHOW FULL FIELDS IN "TableName". From the looks of things these results aren't cached either - so I end up with many (many many many) repeated queries. 

Cheers,

Marcus

[Sam Minnée]

Sounds like a bug, are you able to trace it?

--
You received this message because you are subscribed to the Google Groups "SilverStripe Core Development" group.
To post to this group, send email to silverst...@googlegroups.com.
To unsubscribe from this group, send email to silverstripe-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/silverstripe-dev?hl=en.

[Marcus Nyeholt]

Okay, have traced it back to this commit - https://github.com/silverstripe/sapphire/commit/2f00884e792f3c9a8fb4c2ea992b516fcd8e08a9#L1R185

That calls $db->query - which for me is triggering a couple hundred times each request. Not sure what the best place to cache this value out would be though

Cheers,

Marcus

[Sam Minnée]

Hamish, are you able to look at this, since it's your commit?

[Hamish Friedlander]

Ah,

Yeah, we'll need to cache that value. Theoretically we only need to invalidate the cached value every time a /dev/build is run, but just a static ad-hoc cache will do for now - I'll take a look in a bit.

Hamish Friedlander