[development] No last access?

Carl Mc Dade carl_mcdade at yahoo.com
Mon Feb 12 16:21:44 UTC 2007

Nope, That is updated first so their is no way of pulling the old time code before the newer on sets. This is the same problem as the access object. As matter of fact the login ia updated a split second before the access time.

access = 1171296985
login= 1171296984 
 Carl Mc Dade
Web Developer


----- Original Message ----
From: AjK <drupal at f2s.com>
To: development at drupal.org
Sent: Monday, February 12, 2007 4:57:43 PM
Subject: Re: [development] No last access?

> Is there no longer a last access functionality?
> using the global user and calling $user->access
> gives the value after the database has been updated.
> Not the value in the database at the time of login.
> Ex. the value in the database table is 0000002.
> You will not get this value but the value 0000003
> which is the time of the latest access.

The above was your original question.....

> No luck with that. Time code shown in
> database = 1171293946 timecode called by
> using the following
> print $account-access;
> 1171294179

Erm, am I missing something here or should you not be doing:-

print $account->login;

"login" holds the timestamp of the last login, "access" holds the timestamp
of the last browser hit for the user.

This is from user.module:-

  // Update the user table timestamp noting user has logged in.
  db_query("UPDATE {users} SET login = %d WHERE uid = %d", time(),

and this is from session.inc:-

  db_query("UPDATE {users} SET access = %d WHERE uid = %d", time(),


TV dinner still cooling? 
Check out "Tonight's Picks" on Yahoo! TV.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20070212/471a8881/attachment-0001.htm 

More information about the development mailing list