grr/server/grr_response_server/stats_store.py
def _ShouldUseRelationalDB():
  """Returns True iff storage of stats data in the relational DB is enabled.

  As far as the relational-DB migration is concerned, it isn't worth it
  to have a dual-writes stage for stats, given the short-lived nature of
  the data, i.e we should either exclusively use the legacy DB or the
  relational DB.
  """
  return data_store.RelationalDBReadEnabled(category="stats")
Returns True iff storage of stats data in the relational DB is enabled.

  As far as the relational-DB migration is concerned, it isn't worth it
  to have a dual-writes stage for stats, given the short-lived nature of
  the data, i.e we should either exclusively use the legacy DB or the
  relational DB.
  
Returns True iff storage of stats data in the relational DB is enabled.
As far as the relational-DB migration is concerned, it isn't worth it
to have a dual-writes stage for stats, given the short-lived nature of
the data, i.e we should either exclusively use the legacy DB or the
relational DB.
Returns True iff storage of stats data in the relational DB is enabled . As far as the relational - DB migration is concerned it isn ' t worth it to have a dual - writes stage for stats given the short - lived nature of the data i . e we should either exclusively use the legacy DB or the relational DB .
def _ShouldUseRelationalDB():
  return data_store.RelationalDBReadEnabled(category="stats")
def _ShouldUseRelationalDB ( ) : return data_store . RelationalDBReadEnabled ( category = "stats" )
Returns True iff storage of stats data in the relational DB is enabled.
Returns True iff storage of stats data in the relational DB is enabled .
"""Returns True iff storage of stats data in the relational DB is enabled.

  As far as the relational-DB migration is concerned, it isn't worth it
  to have a dual-writes stage for stats, given the short-lived nature of
  the data, i.e we should either exclusively use the legacy DB or the
  relational DB.
  """