23455 Posts in 18904 Topics by 2877 members
|Go to End|
17 June 2014 at 2:24am
I'm pretty sure this would have been discussed before, but the remove of both extendedSQL() and buildSQL() has made it almost impossible to upgrade without implementing this functionality in the way it existed before.
The docs state, "this facility was error prone" which is the reason for the removal if I'm correct?
Surely, we should have the choice on whether we want to risk using these methods or not.
In a website that is vastly more complex than what meets the eye, you can't possibly, and will never cover all bases for why these methods may be used, and in trying to do so you create error prone situations by overcomplicated code.
Does anyone else feel these methods should be added back in?
17 June 2014 at 4:13pm
Hey Bonner, It might be a good time to point you in the direction of the developer list (A google group to discuss higher level ideas about the Framework and CMS). This might be a good question to raise in that space I think you would be more likely to get a deeper and more technical response.
17 June 2014 at 9:51pm
Thanks for the link, believe it or not in the 10 years I've been a developer I've never used Google groups
I'll make a swift move over there and contribute where I can.
|Go to Top|