No node updated argument?

Thanks - np. The API docs are great - I'll just need to allocate more time to understanding how it works. =)

As you said, this was relatively trivial to achieve. I realised, after I did it, that it didn't actually fully meet my use case, but it's a start! =)

Apologies for not creating a patch - using Microsoft TFS for source control here and it doesn't support creating patches. Anyway, here is the code to add it straight in to 'node.views.inc' (line 121) if you would like to:

  // changed field
  $data['node']['changed'] = array(
    'title' => t('Updated date'), // The item it appears as on the UI,
    'help' => t('The date the node was last updated.'), // The help that appears on the UI,
    'field' => array(
      'handler' => 'views_handler_field_date',
      'click sortable' => TRUE,
    ),
    'sort' => array(
      'handler' => 'views_handler_sort_date',
    ),
    'filter' => array(
      'handler' => 'views_handler_filter_date',
    ),
    'argument' => array(
      'field' => 'changed',
      'handler' => 'views_handler_argument_node_created_fulldate',
    ),
  );

Or, alternatively, replace the node.changed handlers in your own module:

/**
 * Implementation of hook_views_data_alter()
 */
function yourmodule_views_data_alter(&$data) {
  // changed field
  $data['node']['changed'] = array(
    'title' => t('Updated date'), // The item it appears as on the UI,
    'help' => t('The date the node was last updated.'), // The help that appears on the UI,
    'field' => array(
      'handler' => 'views_handler_field_date',
      'click sortable' => TRUE,
    ),
    'sort' => array(
      'handler' => 'views_handler_sort_date',
    ),
    'filter' => array(
      'handler' => 'views_handler_filter_date',
    ),
    'argument' => array(
      'field' => 'changed',
      'handler' => 'views_handler_argument_node_created_fulldate',
    ),
  );
}

I've taken the latter approach for now, to keep the Views core clean in case this is in the next release. =)

Oops. Changing status.