Re: Multiple instances of mysql_connect() in single PHP document.

On Tue, Nov 10, 2009 at 4:14 PM, Timothy Legg <php_list@timothylegg.com> wrote: > > Hello, > > Is it wrong to have mysql_connect() called twice within a single PHP > document, such as this?  I have been running into some fairly annoying > query failures that commute when I change the order of these two blocks of > code.  I am currently working around this by repeatedly using > mysql_select_db() to change the databases as I am needing to change to a > different database. > > To be more specific, I can use the $db_material handle in doing a query, > but it will always try to search in the Labor_Log table and thus fail > because the tables have different and names.  Swapping these blocks will > have a vice-versa effect. > > >        //Connect to server (materials) >        $db_material = mysql_connect("localhost", "root", > "secret"); >        if (!$db_material) >        { >                echo( "<P>Unable to connect to the database server at this > time.</P>" ); >                exit(); >        } >        mysql_select_db("Material_Log", $db_material); > > >        //Connect to server (labor) >        $db_labor = mysql_connect("localhost", "root", > "secret"); >        if (!$db_labor) >        { >                echo( "<P>Unable to connect to the database server at this > time.</P>" ); >                exit(); >        } >        mysql_select_db("Labor_Log", $db_labor); > > > > Tim Legg > > > -- > PHP Database Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > If the databases are in the same mysql server, then you could qualify the table select with the database name and simply re-use the connection select db_name.table_name.field from db_name.table_name [where] -- Bastien Cat, the other other white meat