RE: [PHP] Re: catch the error
| From: | Boyd, Todd M. | Date: | Thu, 26 Feb 2009 22:34:20 +0000 |
| Subject: | RE: [PHP] Re: catch the error | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-288884@lists.php.net to get a copy of this message | ||
> -----Original Message-----
> From: Chris [mailto:dmagick@gmail.com]
> Sent: Thursday, February 26, 2009 4:16 PM
> To: Boyd, Todd M.
> Cc: PJ; PHP General list
> Subject: Re: [PHP] Re: catch the error
>
>
> > In examples sent to you, people foolishly replaced your $db var with
> > $db_connect ONLY FOR PART OF THE SCRIPT. You've defined your
database
> > connection as $db_connect in some versions of the source, but then
> you
> > reference $db (without _connect) in your mysql_select call in that
> same
> > source.
> >
> > $db = mysql_connect([option list here]); # <-- this code
instantiates
> a
> > connection
> > mysql_select_db([some name], $db); # notice how $db is here?
> > $result = mysql_query([some query], $db); # it's here, too!
> >
> > $db becomes your resource link when you use mysql_connect. That
> resource
> > link must then be passed to your mysql functions. Otherwise, they
> have
> > no idea which database connection you are attempting to use.
>
> RTFM?
>
> If no connection is specified, the last one is used.
>
> It is an optional argument (only *really* needed when you have
multiple
> connections in the same script).
RTF E-mail I sent?
He had used $db_connect instead of $db. $db_connect hadn't been set to
anything. He was specifying a connection, but it was null. Unless it
falls back to the last connection used in the case of an empty variable,
then this was most likely (read: proven to be) the problem.
:p