node_access_realm table?

We encourage users to post events happening in the community to the community events group on https://www.drupal.org.
robertDouglass's picture

http://osinet.typhon.org/riff.org/blog/2006_05_14_data_model_for_drupal_...

His comment on node_access_realm was very interesting. Anyone want to try it and do some profiling? OG module would be a good use case to profile.

Comments

Seems like a good idea

robertDouglass's picture

more I think about it, the more I like it. You query the node_access_realm table once to get the list of realms and define a constant with them, then you have OG_REALM (an integer) for all the subsequent queries. Very fast.

short strings

moshe weitzman's picture

these are very short strings. does it really matter? this seems like a general issue with strings versus integers and not specific to node_access_realm

FB artifact

fgm@drupal.org's picture

Hi all,

As I explained on my blog, it's an artefact of the Firebird port for Drupal: Interbase/Firebird having very stringent limitations on total key width, it is not feasible to use the current schema with the looooong composite key in node_access.

I didn't benchmark what it could mean for other DBMSs, but overall, I've always found better results from DB schemas using shorter keys (typically surrogate) as opposed to composite "nature" keys.

It would indeed be interesting to have a high volume try it to obtain definitive results.

Off Topic

drob's picture

I couldn't help but mentioning that I have fond memories of Interbase which I used for a job at MCI :)