PostgreSQL support

Ok in testing this out on a virgin install I found a couple of other problems that this patch re-roll fixes as well as verifying PostgreSQL support via some query changes.

First off, the module should have a dependency on profile module since it is based on storing data in profiles. Got caught on that one.

Second, I was using the content_types() function call to get the list of node types but that's a CCK function and when tried on a virgin install it failed. So I changed that to use node_get_types() which should still give the same results.

Third, in testing on PostgreSQL I found a couple queries that wouldn't work as is. This patch has been tested on MySQL and PostgreSQL and the new queries are successfully run on both.

One caveat is that this was not tested with the workflow support. I can eyeball real quick that at least one of the queries that uses UNIX_TIMESTAMP() will fail in PostgreSQL as that is not implemented in PostgreSQL at least with that command name.

that is in user_stats_cron() here

  // Fire workflow_ng daily anniversary event
  if (module_exists('workflow_ng')) {
    $sql  = "SELECT uid FROM {users} u ";
    // ((last cron - created) - (time() - created)) > one day
    $sql .= "WHERE ";
    $sql .= "(FLOOR((unix_timestamp()-created)/(60*60*24))-FLOOR((%d-created)/(60*60*24)))>0 ";
    $sql .= "AND uid>0 ";
    $result = db_query($sql, variable_get('cron_last', time()));
    $reset_user_count = 0;
    while ($update_user = db_fetch_object($result)) {
      $user = user_stats_user_load($update_user->uid);
      // We stop at 50 reset users (they'll just have to wait) so cron doesn't get timed out
      if (!isset($user->user_post_count) && $reset_user_count < 50) {
        user_stats_post_count_update($user, 'reset');
        $reset_user_count++;
      }
      workflow_ng_invoke_event('user_stats_day_older', $user);
    }

I am on holiday tomorrow so I can pick this back up when I return.

I've updated to the latest user_stats and I see that you reworked the .install a bit. Unfortunately some of the queries are not compatible with PostgreSQL.

See attached patch for reworked version