graphql-python / graphql-python/graphene
Graphene Having Two DjangoObjectType of same Model
- Langage dominant
- Python
- Étoiles
- 8.2k
- Forks
- 818
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
Hi, I am new to graphene and my company has big application running over django and graphene. I have to segregate some services but that takes djangoobjectype with a model which has been defined already in another django app.
Bascially :
MyClassTypeA(DjangoObjectType:)
ModelA
MyClassTypeB(DjangoObjectType)
ModelB
while querying, from class type A, i realize that class type B overrides classtype A It causes other app not fetching data properly as query of class a reads from b.
What I want is both class doesn't interfere with each other while querying . Something like creating multiple seriailzerclass of same model with different classname which works independently.
Or can i easily inherit previous class and add some custom field .
I checked the docs and didn't get proper solution. DO we need to define Django object type of same model only once? I need duplicate djangoobjectype of different class name of same model.
Any help of this will be appreciated.
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Piste de recherche
Start by reviewing how the two DjangoObjectType definitions are registered and resolved when they reference the same Django model. Reproduce the conflict with the MyClassTypeA and MyClassTypeB scenario, then determine whether both types can query independently or whether inheritance and custom fields provide the intended separation.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- graphql, python
- Domaine
- api, backend
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- À clarifier
- Accessibilité débutants
- 25/100