-
Notifications
You must be signed in to change notification settings - Fork 82
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
TypeORM future? #212
Comments
Hi @capioc, So it is not a problem that typeORM is almost dead. Besides we are now development the new nhipster 2.0.0 with vuejs and improvements #211 |
Hi @amanganiello90 , thanks for the prompt reply! I know that NHipster is so much more than TypeORM, but it's such a crucial part of its architecture. I am not implying that NHipster is going to die. I was just beginning a new project and after using JHipster at work I really wanted to give NHipster a try. However, I saw that TypeORM having so many open issues and a discussion that its maintenance is not sustainable and consistent. And a lot of people don't feel confident to use it for new projects. That's why I wanted to hear your opinion on that and if there are thoughts to integrate a different ORM solution in the future. |
At this moment the typeORM usage in NHipster covers all the features (sql, relationship and mongodb). So for now there aren't problems in NHipster for its. Maybe in future if it is necessary, we could evaluate another solution, but now I don't know. |
Alright thank you very much! I will start my project with NHipster and I will report back if any issue arise |
For nodejs there are these other following ORM project used in backend development:
Nothing has the db support as TypeORM (it supports al lot of database with robust relationship mapping). If you could suggest any other solutions, it will be great. |
I hope that my explanation is been clear. So I consider this question/issue resolved. |
Considering the state of TypeORM project, the development of which is almost dead, what is its future regarding nHipster?
Is it still considered stable and production ready?
Thank you
The text was updated successfully, but these errors were encountered: