My Toolkit

Posts

If you haven’t ever checked out Drupal’s relational database, you’re in for a good scare. You might assume that each node would be a row in a table and when you visit a page, the node is retrieved and rendered from that single row. Well, actually, Drupal keeps data from every field on that node in a separate table. If you care to check out the tables in MySQL, you’ll see ones called field_data_field_body and field_revision_field_body. The entries in those tables each have a node id reference, field value, field language and some other information you probably don’t care about. Since any “body” field requires the exact same information regardless of which node it appears in, Drupal stores all body content in this one table. Pretty cool right?

So I was checking out the new data structures layed out in EcmaScript 6 today and found the WeakMap. My mind skipped to the limited coding I’ve done in Objective C and the whole non-atomic vs atomic properties thingy – which was which again?