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

Unique violation error becomes WLValidationError with invalid attr #5658

Closed
SamuelMarks opened this issue Jul 11, 2017 · 7 comments
Closed

Comments

@SamuelMarks
Copy link

Waterline version: 0.12.2
Node version: v8.1.3
NPM version: 5.2.0
Operating system: darwin x64


Fix: balderdashy/waterline#1507

@sailsbot
Copy link

@SamuelMarks Thanks for posting, we'll take a look as soon as possible.


For help with questions about Sails, click here. If you’re interested in hiring @sailsbot and her minions in Austin, click here.

@sgress454
Copy link
Member

@SamuelMarks Can you elaborate on what the issue is, and on how your PR fixes it?

@SamuelMarks
Copy link
Author

@sgress454 I was getting these errors: Invalid attributes sent to undefined:\n • 0\n.

By applying that aforementioned patch I know get the proper error, which is this case was a unique violation error.

@sgress454
Copy link
Member

sgress454 commented Aug 10, 2017

@SamuelMarks Under what conditions were you getting the error? Can you post what database adapter you're using (sails-mysql, sails-postgresql, etc.) and its version, along with the code for your model and an example of some code (I'm assuming it's a .create() or a .update() call) that I can use to reproduce the issue? Just want to make sure I have all the info.

@sailsbot
Copy link

@SamuelMarks,@sailsbot,@sgress454: Hello, I'm a repo bot-- nice to meet you!

It has been 30 days since there have been any updates or new comments on this page. If this issue has been resolved, feel free to disregard the rest of this message and simply close the issue if possible. On the other hand, if you are still waiting on a patch, please post a comment to keep the thread alive (with any new information you can provide).

If no further activity occurs on this thread within the next 3 days, the issue will automatically be closed.

Thanks so much for your help!

@sgress454
Copy link
Member

@sailsbot I think this is still a thing, just waiting for some more info...

@sailsbot
Copy link

@SamuelMarks,@sailsbot,@sgress454: Hello, I'm a repo bot-- nice to meet you!

It has been 30 days since there have been any updates or new comments on this page. If this issue has been resolved, feel free to disregard the rest of this message and simply close the issue if possible. On the other hand, if you are still waiting on a patch, please post a comment to keep the thread alive (with any new information you can provide).

If no further activity occurs on this thread within the next 3 days, the issue will automatically be closed.

Thanks so much for your help!

@johnabrams7 johnabrams7 transferred this issue from balderdashy/waterline May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants