[#3959] - Joomla database
- Closed
- 13 Sep 2014
- Medium
- Build: master
- # 3959
What is the point of being able to specify a class on database object methods fetchObject and loadObjectList if the a class like JTableWhatever can't be instantiated without a database object and doesn't accept null ?
True, but with the DI we could make this work? The DI would build the table and then set properties on it?
The DI code is still awfully new in Joomla and nothing has really been refactored to use it.
Can this be closed?
Is there an implementation of such feature? At the minute my code has to accept null in the constructor and will get from factory which isn't favoured. Dependency injection when implemented and this then doable, then my issue will be solved.
Unless you have an issue with it being open and/or have another solution?
—
Sent from Mailbox for iPhone
On Wed, Aug 27, 2014 at 11:19 AM, Brian Teeman notifications@github.com
wrote:
Can this be closed?
Reply to this email directly or view it on GitHub:
#3959 (comment)
zero-24
- | Status | New | ⇒ | Known Issue |
Set to "closed" on behalf of @vdespa by The JTracker Application at issues.joomla.org
| Status | Known Issue | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2014-09-13 13:28:07 |
Closed, this basic functionality isn't going be implemented? Injecting the database instance... Open to me implementing this and doing a PR?—
Sent from Mailbox for iPhone
On Sat, Sep 13, 2014 at 2:28 PM, jissues-bot notifications@github.com
wrote:
Set to "closed" on behalf of @vdespa by The JTracker Application at issues.joomla.org
Reply to this email directly or view it on GitHub:
#3959 (comment)
I have marked it as a known issue. Leaving it "Open" will unfortunately not fix it. If somebody has an idea, a PR would be the best approach to move forward. Thanks for understanding.
This comment was created with the J!Tracker Application at http://issues.joomla.org/.
| Labels |
Added:
?
|
||
Well at least in the case of
fetchObject(using the MySQLi driver as my example), the mysqli_fetch_object function it's wrapping is the same way. So inherently it's probably a case of the wrapper not having more complex functionality than what it's proxying to.