Any reason you don’t just do something like

cookieName=”pl” (for persisted login)
cookieValue=”BigRandomGarbagesdffjkshjdifhioshdfijsdfjisdjfsdf”

I can’t see any good reason for two DB fields, could you explain your reasoning a bit more?

Thanks,

Craig

Thanks for this post, I think I’ll be using the Countable interface sometime.

You say

Countable can also be used to signal the state of an object.

and

the further you move the count() method away from this functionality the less intuitive the code becomes

I’d argue that you didn’t heed your own warning . The example with the Countable records that were live was better imho.

Thanks again for the post!

Thanks for the comment. I don’t think that either example you post is better than the other: both are totally valid and how you use the count() method is entirely down to the developers taste. I personally prefer calling the count() method through the count function though. One of the primary purposes of the predefined interfaces is to allow you to hook into and to override core PHP behaviour so to me implementing Countable and then not using it through the count function just feels wrong. However, that really is just my subjective opinion for what it’s worth!


if (count($obj)) {
//$_data is not null, proceed accordingly.
}


better then writing:


if ($obj->count()) {
//$_data is not null, proceed accordingly.
}


?