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.

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

ACID compliance, rollback, joins, associations, arbitrary SQL #1235

Closed
Vandivier opened this issue Apr 4, 2018 · 4 comments
Closed

ACID compliance, rollback, joins, associations, arbitrary SQL #1235

Vandivier opened this issue Apr 4, 2018 · 4 comments
Labels

Comments

@Vandivier
Copy link

Description / Steps to reproduce / Feature proposal

Feature proposal!

Current Behavior

Loopback doesn't have associations https://www.netiq.com/communities/cool-solutions/handling-move-events-and-associations-loopback-driver/

Loopback has trouble with or lacks acid compliance including rollback (unlike, say, Sequelize) https://stackoverflow.com/questions/34965732/how-to-implement-acid-transactions-in-loopback#38231272

Expected Behavior

  1. enforce associations for sql
  2. Acid compliance for SQL
  3. I want to be able to execute arbitrary SQL including flavor-specific queries like SELECT NOW() seamlessly within Loopback instead of having to use two DB management solutions in one app.

See Reporting Issues for more tips on writing good issues

@dhmlau dhmlau added the non-DP3 label Apr 20, 2018
@dhmlau dhmlau removed the non-DP3 label Aug 23, 2018
@hvlawren
Copy link

hvlawren commented Dec 4, 2018

In our loopback 3 app, we had to execute some native sql to use some Postgres specific queries (e.g. https://www.postgresql.org/docs/9.6/functions-textsearch.html) for features in some cases (like the fuzzy text matching) and for performance in other (complex multi table joins with many rows per table). Having a more elegant way to do this would be nice.

@stale
Copy link

stale bot commented Nov 29, 2019

This issue has been marked stale because it has not seen activity within six months. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository. This issue will be closed within 30 days of being stale.

@stale stale bot added the stale label Nov 29, 2019
@stale
Copy link

stale bot commented Dec 29, 2019

This issue has been closed due to continued inactivity. Thank you for your understanding. If you believe this to be in error, please contact one of the code owners, listed in the CODEOWNERS file at the top-level of this repository.

@stale stale bot closed this as completed Dec 29, 2019
@achrinza
Copy link
Member

Related: #2331

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants