Prisma

<@U0RQY0KK5> Here it says you can use the float type - what does that mean? <https://www.graph.cool/forum/t/insert-object-in-a-relation-at-given-index/860/2>

so, instead of using integer positions 0, 1, 2, you could use float positions 1, 1.5, 2, 2.5, 3, so reordering items is easier

Ohh - so there is no way to maintain order with a list of related items?

I was hoping it was like an array where the last item was the last added

that's not how it works - the nodes need to encode their position

alternatively, you store a list of strings, which are the ids of the separate items

makes sense - so I’d need to make another Type for my cart rather than just holding it it directly

with Strings, can I still populate with graphql?

I think in your case it's fine to put `position` on `Item`

would position not be shared by everyone with that item in their cart though? or is it not updated?

that's true! I thought you are creating new items for every cart :slightly_smiling_face:

hmm okay -so only way is to make another type then

is there a reason you are not using separate items per cart?

Maybe I’m missing something - I have Items and I just add them to the users cart. You are suggesting copying the item when someone adds it to their cart?

Hey <@U6KUJ0RDF> - Here is what I have for my Cart schema…

```
type Cart {
  id: ID! @isUnique
  items: [CartItem!]! @relation(name: "CartItems")
  createdAt: DateTime!
  updatedAt: DateTime!
}

type CartItem {
  id: ID! @isUnique
  orderedItem: Variant! @relation(name: "OrderedCartItem")
  quantity: Int @defaultValue(value: 1)
  cart: Cart @relation(name: "CartItems")
  createdAt: DateTime!
  updatedAt: DateTime!
}
```

`OrderedItem` is a relation to the `Product` (or Variant in my case)

yea and if you would add a field `position` to the `CartItem` type of <@U4RHJB44A>, you could sort the items specific to one cart

<@U4RHJB44A> so you have three types then, right? Cart, CartItem and Item?

ah, maybe this is what you meant before. yes, the idea is to have item "templates" that contain the meta data like name, description and price

Yeah makes sense - I think I’ll go that route

while the item in a cart only contains the quantity and the position

and then to associate that with a user, it’s a 4th type

was hoping I could only do it with 2 types - oh well

That’s right <@U6KUJ0RDF> - I struggled trying to come up with a similar thing. There is even a problem with this approach if you stop at this level, but what I’ve decided to do is when an order is created, copy the values to Order and OrderItem’s. as a orderedItem could change or be deleted, that would mess things up in the future. 

thanks for the help :slightly_smiling_face:

<@U4RHJB44A> is a webshop champ :smile: :100: