-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add namespacing/modules #579
Comments
... the simplest possible solution could be to extend the |
@pkarw , the issue I see here is that currently code like |
On the other hand, what I think we could do is to have a way to return a MySQL object which has a number of fields, each of them being a function (e.g. field |
This way we could have:
|
@czerwinskilukasz1 good point. I think it's a great way to go for this FR; it's somewhat clarifying the #580 as well (I mean the "dot" notation could be used to have both #579 and #580 up) |
Blocked by #589 |
Is your feature request related to a problem? If yes, please describe the problem.
When we'd like to implement a more broad set of the resources/integrations we'll encounter a namespacing issue, kind of modules/namespaces/groups would be a handy solution to it.
For example when we'd like to develop the resources for accessing
MySQL
andMongoDB
both ORM modules could potentially have a method likemysql:findOne({})
/mongodb:findOne({})
. There's actually no way for avoid resource overlapping other than naming convention (egmysql_findOne()
- which actually is not an elegant solution)The text was updated successfully, but these errors were encountered: