Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ORM Independence #117

Closed
ritch opened this issue Apr 11, 2017 · 3 comments
Closed

ORM Independence #117

ritch opened this issue Apr 11, 2017 · 3 comments
Labels
Juggler

Comments

@ritch
Copy link
Contributor

ritch commented Apr 11, 2017 •
edited
Loading

ORM independence. Let's face it, writing and maintaining a good ORM is a lot of work, and in all honesty, I think we are pretty much failing at that. I would like to make it easy for LoopBack users to switch to a different ORM/data-access library when their needs outgrow the basic ORM capabilities we provide in LoopBack.
-- @bajtos
Closed
@bajtos bajtos mentioned this issue Apr 21, 2017
Merged
@bajtos
Copy link
Member

bajtos commented Jul 18, 2017 •
edited
Loading

An example showing how to talk to database from controllers, bypassing juggler: https://github.com/strongloop/loopback-next-example/tree/413e7533d023d3042592b62935abf62d04527ced/services/account-without-juggler

@dhmlau dhmlau added the Juggler label Sep 6, 2017
@dhmlau
Copy link
Member

dhmlau commented Sep 6, 2017

relate to: #537

@bajtos
Copy link
Member

bajtos commented Nov 3, 2017

This has been already done, see http://loopback.io/doc/en/lb4/Repositories.html#persisting-data-without-juggler-using-mysql-database ✌️

@bajtos bajtos closed this as completed Nov 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Juggler
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@ritch @bajtos @superkhau @dhmlau