[Tickets #9151] Re: Kronolith, Nag, Mnemo, Turba don't work with Oracle DB

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9151
------------------------------------------------------------------------------
  Ticket             | 9151
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Kronolith, Nag, Mnemo, Turba don't work with Oracle DB
  Queue              | Horde Framework Packages
  Version            | FRAMEWORK_3
  Type               | Bug
  State              | Feedback
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             | Jan Schneider, Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2010-07-29 15:13) wrote:

Yes, we purposefully set the conncted_database_name to '' in the sql  
share driver. This is to workaround an issue with MDB2  not being able  
to detect when a database connection changes external to it's code.  
See Bug: 6997 for more detail on this.  What is supposed to happen is  
MDB2 re-selects the database in this case. That is what the commented  
out code is doing. I have no idea why it's failing, as  
$this->database_name should be the correct name to connect to. That  
being said, I'm no oracle expert, so I can't speak to the correctness  
of the statement being performed there.

See if you can add the line:

var_dump($result);

right before the PEAR::isError() statement to see if you can get a  
more detailed error message. Unfortunately, if the issue is with code  
in this file, it's not a Horde issue - as this is from PEAR.