Support for remote Databases ?? Support for remote Databases ??
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

Support for remote Databases ??

Started by casNuy, February 04, 2006, 03:52:13 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

casNuy

In release 3.2 I actually removed support for external databases, meaning a Coppermine Database on a remote server.
It clearly supports the use of 2 databases as long as the PostNuke DB user has access to the Coppermine database.

My questions are:

Do you need the option of being able to connect to a remote Coppermine database?
Is there a problem with giving the PostNuke DB user access to the Coppermine database ?

Thanks for your feedback !!

Cas

TomG

Yes, I need access to a separate coppermine database that is on the same server but is forced to have a different username (the same username is not allowed for 2 databases on my host, so I can't add the PostNuke user to the coppermine db). So there has to be a way to allow a separate username and password for the coppermine database, even if it is on the same server.

Tom
www.lightpainter.co.uk
www.edinburghphotographicsociety.co.uk

casNuy

I will add this feature back into pnCPG.

Unless requested otherwise will be part of version 4.0 which should also have support for cpg_NG

Cas

Joachim Müller

cpgNG is still in a very early stage, I wouldn't recommend building pnCPG to support it. In fact, I wouldn't even mention it in the pnCPG docs.

casNuy

In that case I will park it and release another 3-version.
So it will be part of 3.3 which is currently being tested by Tom.

Cas