On Tuesday, July 2, 2002, at 04:31 PM, Richard Lynch wrote:
> Well, yeah, at that point all you have is SQL and Result, because the
> function has no idea what that SQL is about in any given call...
>
> But, personally, I just don't see the point to having a function/class
> do my
> database w
Portability between different databases makes a DB class beneficial. Then
again, I stick with MySQL, so I don't bother with the extra overhead either.
-Original Message-
I just don't see a cost/benefit ratio that makes sense in the DB classes.
I know it's a minority opinion, but I've ne
>But once I had moved most of my code into object methods and functions
>(and therefore out of the global namespace/scope/whatever), I realized
>this really didn't matter as much. In fact, for consistency and
>neatness, it was better that I use only $sql or $result, since there was
>only ever
On Tuesday, July 2, 2002, at 03:04 AM, Richard Lynch wrote:
> And, really, $result is about a generic a variable name as $i
>
> How about using $user_info or even $user_info_result?
>
> Yes, I know every example and every PHP book on the planet uses $result.
> That doesn't make it right :-)
I
>1. I know that you initially begin the session with the session_start()
>function. Is this function required on all pages in order for the session
>variables to remain globalized?
Yes -- on all pages that intend to use sessions.
If you have a page "in between" that has no use for session da
5 matches
Mail list logo
