Populate filter passes along single digit values only

Tried forcing it with a form_alter which changes what's displayed in the filter, but doesn't fix the query.

function MODULE_form_views_exposed_form_alter(&$form, &$form_state) {
  $f = 'FIELD';
  if(array_key_exists($f,$form)) {
    $form[$f]['#value'] = '9999';
  }
}

Confirmed that the query always gets only a single digit via pre_execute. Even when exposed and a new value (like 777) is entered, it comes through as 7 in the query.

function MODULE_views_pre_execute(&$view) {
  switch($view->name) {
    case 'MYVIEW' :
      dsm($view->build_info);
      dsm($view->query);
      break;
  }
}

Hmmm...
Confirmed that the correct value IS being passed from the exposed populate filter into the real fields via dsm($view->filter); as well as all the "exposed" view attributes ie. $view->exposed_input at both the pre_execute and pre_render hook level.

It's in $view->build_info where the value has changed to single digit. Assuming this is a good indicator of where the problem is, but not where to go next.

typos

The query build must truncate this value. However, everything seems fine all the way through views_filters_populate_handler_filter.inc

I can get the value through the view by forcing it into the query (just for testing, because this is gross) with a hook_views_query_alter().

function MYMODULE_views_query_alter(&$view, &$query) {
  switch($view->name) {
    case 'MYVIEW' :
      $value = ($view->exposed_input['MYFILTER']) ? $view->exposed_input['MYFILTER'] : 9999; // my default
      $query->where[1]['args'][0] = $value;
      $query->where[1]['args'][1] = $value;
      break;
  }
}

improve title

Awesome.
Glad my thoroughness made it solvable :)
I'll just leave my hack in place until you do the new release. Let me know if you do actually need a test.
Thanks.