Re: DataObject tweak ok with DB and MDB2
| From: | Alan Knowles | Date: | Thu, 07 Apr 2005 11:32:48 +0000 |
| Subject: | Re: DataObject tweak ok with DB and MDB2 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 | Groups: | php.pear.general php.pear.general |
| Request: | Send a blank email to pear-general+get-18624@lists.php.net to get a copy of this message | ||
$opts = &PEAR::getStaticProperty('MDB2', 'options');
$opts = array('portibility'=>0);
Should work - the code is quite expicit about where it's getting stuff
from (and why) now.
Regards
Alan
On Thu, 2005-04-07 at 20:48 +1000, Dan Rossi wrote:
> On 07/04/2005, at 8:22 PM, Lukas Smith wrote:
>
> > Dan Rossi wrote:
> >
> >> So what are you saying we should do with $db_options ? portability is
> >> on by default which is not so good for me. what is more readable and
> >> definable as a key userID or userid ... :)
> >
> > well I would say let the user specifiy the options and not worry about
> > it in DB_DO.
> >
> >
>
> Hence the need for the $db_options setting to be sent to MDB2. There
> was the issue with my hack of sending the MDB2 specific db_options
> settings via a nested array in the DataObject config settings, i am
> sending it currently via my xml settings like
>
> <DataObject>
> <MDB2>
> <portability>0</portability>
> <MDB2>
>
> </DataObject>
>
> then seting $db_options = MDB2 settings here
>
> I had no problems with it, it works but other people may have issues ;)
> Its also illogical to set the getStaticproperty on the application
> class level as with the dbdo , it works but then you have to specify
> which DB class you are using twice :)