For example I want:

type Location {
  longitude: Float!
  latitude: Float!
}

I don't want this as a table, I just want to use it on another type:

type Post {
  ...
  location: Location!
}

Any ideas?

You’re mixing your datamodel and your GraphQL schema. Prisma’s GraphQL API should not be used directly, but rather using a GraphQL API that you’ll create on top of it. If you want a Location type that isn’t in your database, then you have to add it on the schema of your GraphQL server that seats on top the Prisma’s one

So for anything like that I should just use a Json type?

you should use a prisma with mongodb probably

How's that make a difference to my problem.

it will allow you to do what you are refering too

I don’t get it, how will a JSON type solve your problem? You want to expose a type that is not in your database. You cannot do that from your datamodel

I am using graphql yoga.

But you explicitely said that you didn’t want to store it in your database

are you referring to an embedded

Where did I say that? I literally said I'm storing it in PostgreSQL as a JSON type.

I don't know about PostgreSQL

I misunderstood your problem, apologies. By not having a table, I thought that was a way to say you didn’t want to store it. Then yeah, a JSON type is probably the way to go for now, unless there’s a better way that I’m not aware of

for embedded type

Mongodb might not be a great fit for his use-case here

why not?

I'm not using MongoDB, I'm using PostgreSQL.

Because MongoDB is not a relational db and have different use-cases than document-based db To sum-up here daryl (and forgive me for not understanding your problem), yeah, you should probably go with a json type. AFAIK, postgres does index

jsonb

, but I don’t know whether Prisma uses

json

or

jsonb

internally

Sucks though because a Json type can be anything

But the problem here is not prisma but rather what you’re trying to achieve. You’re basically trying to emulate an embedded type which is a concept of document-based db, not relational ones

Yeah I suppose

What’s the reason for not wanting a table?

No need to query this data.

Then why is it stored?

Because it's meta.

What’s wrong with having actual tables and just hiding the field from your graphql api that seats in front of the prisma’s one?

I don't like it. Seems silly having redundant tables.