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

Sub-selecting custom fields #419

Open
LydiaF opened this issue Jul 31, 2019 · 2 comments
Open

Sub-selecting custom fields #419

LydiaF opened this issue Jul 31, 2019 · 2 comments

Comments

@LydiaF
Copy link

LydiaF commented Jul 31, 2019

Hi there,

I am sorry if I am missing something big here! I do not even see why this would work but I am completely lost how to go about it :)

I have a big operation that I need to do on the server. It is completely disconnected with the front-end request. I am trying to get some custom fields in a subselection in a prisma query on the backend. This custom field is in the schema but it is not in the prisma data-model; that is why I don't see why it would even work in the first place.

In the picture below, what I have highlighted in the editor is the custom field.

image

I am getting this error:

image

My question is: is it possible to use prisma at all to access these custom fields on the server? If not, can you point me in the right direction? Thank you so much.

@cesarve77
Copy link

How did you solve this?

@LydiaF
Copy link
Author

LydiaF commented Sep 12, 2019

It pained me to do this but I moved the code that resolved these custom fields to where I was trying to get these fields. 😢

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

No branches or pull requests

2 participants