Why is verification token hashed in storage but session id isn't?

[hillac]

From this discussion #1051 (comment) I can see the verification token is hashed to prevent the ability to login as a user in the case db read access is compromised. Is there a reason the same safeguard isn't used for the session id? I don't see the point in protecting the verification token if you can just steal a session. Obviously this isn't that important given you have pretty big issues if your db is compromised.