Hi, As you see this feature is not complete, be patient :) Of cause your notes are good.
Linas Kukulskis Developer [email protected]<mailto:[email protected]> Phone +370 37 333053 Fax +370 37 333054 www.oxid-esales.com<http://www.oxid-esales.com/?campaign=emailsignatur/lt/oxid-esales-com> ________________________________ From: [email protected] [[email protected]] on behalf of Jungclaus, Tobias [[email protected]] Sent: Friday, September 28, 2012 5:10 PM To: [email protected] Subject: Re: [oxid-dev-general] 4.6: new type-parameter in database functions I see, thank you. Beeing curious I searched a little further and found what this is about. Sounds very promising. But wouldnt it be wiser to use the master as default instead of the slave? When slave stays the default, all 3rd party mods that are not adapted will access data through the slave which is faster but less compatible. When adding a new feature through a new optional parameter, the default should always be backwards compatible, which in this case it is not. Tobias Von: [email protected] [mailto:[email protected]] Im Auftrag von Linas Kukulskis Gesendet: Freitag, 28. September 2012 15:09 An: [email protected] Betreff: Re: [oxid-dev-general] 4.6: new type-parameter in database functions Hi, This parameter is preparation for upcoming feature in EE 5.0 version. So in 4.6 you can use just default parameter value, and functions act as usual. Linas Kukulskis Developer [email protected]<mailto:[email protected]> Phone +370 37 333053 Fax +370 37 333054 www.oxid-esales.com<http://www.oxid-esales.com/?campaign=emailsignatur/lt/oxid-esales-com> ________________________________ From: [email protected]<mailto:[email protected]> [[email protected]] on behalf of Jungclaus, Tobias [[email protected]] Sent: Thursday, September 27, 2012 3:29 PM To: [email protected]<mailto:[email protected]> Subject: [oxid-dev-general] 4.6: new type-parameter in database functions Hello oxid devs, when going through the changes in 4.6, I noticed that the function getOne (and execute/select) now has an additional parameter. Most of the times it now looks like : $oDb->getOne( $sSQL, false, false ). The second optional parameter is an array of sql parameters as it had been before. I also found out, what the new optional parameter stands for ($blType = true): it triggers, whether the slave-db or the master-db is used, while default is true = slave-db. But... I have no idea, what that slave or master database thing is... !? And, why is getOne called with (..., false, false) half of the time (so working with the master-db), and the other times without, so using the default slave-db. How do I decide which mode I use in my own modules? Regards, Tobias Jungclaus
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
