Prisma

whats the best way to allow for different types for a field?

```type Concert @model {
  id: ID! @isUnique
  performer: Artist # I would also like to allow for Band here
}```

is that possible? or is there a way to have a base model and extend?

i'm using graphqlgen for the first time today

and my generated types have wacky imports

```
import { Context } from '..\createServer'
import { Item } from './prisma-client\index'
import { User } from './prisma-client\index'
```

i can just go in and change it myself and it works fine from there

also `graphql-yoga`'s `IResolvers` type isn't compatible with the generated `Resolvers` interface made by `graphqlgen`

Can you please create an issue for this in graphqlgen

has anybody else experienced this and know what to do?

hello, i've encountered an error when i do 'docker-compose' up: "Bind for 0.0.0.0:4466 failed: port is already allocated" does anyone know how to fix it?

you might already have something running on that port try `docker ps` to see if it's already running

Anyone having any issues where nested mutation's connnect are losing existing node associations?

I think it might have something to do with postgres because i switched from deploying with a local db to prisma cloud and it’s functioning as expected

hey guys, quick question, regarding search in a Prisma/Yoga powered app, is there a way to use full text search yet when using a postgres db? And is there any update on a Elastic Search implementation?

For now, you can bypass Prisma binding/client in GraphQL resolvers and implement elastic search query using an elastic search SDK. Also, you can use this issue to track the progress of elastic search connector: <https://github.com/prisma/prisma/issues/1665>

thanks for the reply, how difficult would it be to do this?

try it out, then you'll know :smile: it's not a question that has a reasonable answer :simple_smile: 

alright! Can you tell us if the implementation of the elastic search connector is still on track for Q4 then?

Work on the elastic search connector hasn't started yet so it's difficult to say

I think you mitgh have a chance with postgres full text search and executeRaw queries in prisma (undocumented yet)  too <https://www.postgresql.org/docs/9.5/static/textsearch.html>

-.pl

don't know why you're message looks so weird, but this is an issue about your authentication token (CLI authenticates against Prisma Cloud or against Prisma Server) 

it worked really well but from one day to another i was not able to deploy changes to the prisma server …

to the production server i can deploy and to the local too

did you change the management api secret? 

i even deleted the prisma databases and the server

what's the shape of ~/.prisma/config.yml?Please don't share any values, just the shape. 

:wink: the backend serve says this now
java.lang.RuntimeException: ProjectHelper: Could not resolve project with id: visual-knight@test

he should create new one after deleted everything right?

sounds like your fiddling around with stuff and things got inconsistent somehow 

depends on how you deleted everything, how you're persisting stuff etc

"deleting everything" can mean a lot of different things 

its a docker now deplyoment which i delete so the prisma server should be deleted

and databases are just 2 prisma and the deployed one

what I can say is that the original error is likely caused by a syntax error in your config file or some other issue related to your authentication token

prisma deploy just talks to the prisma server with the management secret right?

```
managementApiSecret: PRISMA_MANAGEMENT_API_SECRET
port: 4466
databases:
    default:
        connector: mysql
        port: 3306
        host: SQL_HOST
        user: SQL_USER
        password: SQL_PASSWORD
        migrations: true
        database: prisma
        schema: private
```

i have the same setup for prod and test stage

where was the place where i have to put the management secret inside the configs?

hmm there is no entry in the table CloudSecret after deployment…i think there should one entry with the management secret right?

somebody has any idea what the problem is?
i already deployed prisma new and removed the databases before that

Hey guys, I'm trying to use `graphqlgen` which uses namespaces that are not compatible with babel-preset-typescript, any idea what I should do?

i'm kind of a typescript newbie so i'm not confident enough to create a git issue

but i've isolated my problem before down to the `args` parameter in generated resolver types

&gt; also `graphql-yoga`'s `IResolvers` type isn't compatible with the generated `Resolvers` interface made by `graphqlgen`

image.png

This is the `graphql-yoga` field resolver type

by default the args have the signature `{ [argName: string]: any }`

and this type is generated by `graphqlgen`

this type here is not assignable to GraphQLFieldResolver i think

because i thought that this interface matches that index signature defined in `GraphQLFieldResolver`'s `args`?