Using external db in extension causes problems

Friday 15 September 2006 12:46:46 am

Hi,

I've done it with several dbs and it works (tried it from cronjobs and datatype and modules).

What I do is to close the connection on the external db

      mysql_free_result($result);
      mysql_close($this->_connectionID);

Does it solve your problem ?

X+

http://www.sydesy.com

Friday 15 September 2006 9:40:40 am

You can connect to external DB using eZDB lib.

Here is an example:

include_once( 'lib/ezdb/classes/ezdb.php' );

$dsn = array(
	'server' 	=> 'localhost',
	'user' 		=> 'user',
	'password'	=> 'mypass',
	'database'	=>	'mydb',
	'show_errors' => true
	);

$extdb =& eZDB::instance( 'ezmysql', $dsn, true  );
$extdb->arrayQuery("SELECT * FROM EXT_TABLE");

Then using eZDB lib you may query your external DB without errors. Witn new instance you can still get access to eZ publish current db.

    include_once( 'lib/ezdb/classes/ezdb.php' );
    $db =& eZDB::instance();

See lib/ezdb/classes/ezdb.php for more details.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Monday 18 September 2006 1:24:20 pm

Hi Atte,

Not sure I got you. You mean that you added

   include_once( 'lib/ezdb/classes/ezdb.php' );
   $db =& eZDB::instance();

After your code and it works fine ?

X+

http://www.sydesy.com

Thursday 24 May 2007 6:22:33 am

Revisiting an old post.

The problem is that what I'm working with is an external system using its own database mechanisms and calls. So Lukasz Serwatka's solution above is not feasible without rewriting parts of the other system.

When the external code calls

    mysql_close();

this seems to disrupt eZ publish.

I thought I solved it using

mysql_select_db('ezdatabase');

after the other code.

However, when the external code is called more than once for a template, this also fails.

So now, based on rereading the discussion above, I've worked out the following sollution:

    $dsn = array(
             'server'        => $GLOBALS['eZDBGlobalInstance']->Server,
             'user'          => $GLOBALS['eZDBGlobalInstance']->User,
             'password'      => $GLOBALS['eZDBGlobalInstance']->Password,
             'database'      => $GLOBALS['eZDBGlobalInstance']->DB,
             'show_errors' => $GLOBALS['eZDBGlobalInstance']->RecordError
    );

//..... other code including mysql_close(); does its thing here .....

    eZDB::instance( 'ezmysql', $dsn, true );

It feels sort of hackish, and I'm not sure about using the 'RecordError' variable, but it seems to work.

Any comments or suggestions for better ways of doing this?