manueliglesias
commented
4 years ago Hi @moweex
Any advice how can improve our M2M model to work fine with DataStore.
Your schema is fine, it works as expected, we tested with this sample app and your schema (minus the Building type) provisioned to a back-end.
Note the order of the saves in the addRecordTask function:
- Task
- TimeTrackingRecord
- RecordTask
Schema
type Task @model {
id: ID!
name: String!
icon: String
records: [RecordTask] @connection(name: "TaskRecords")
}
type TimeTrackingRecord @model {
id: ID!
hours: Int!
minutes: Int!
time: AWSDateTime!
# building: Building @connection(name: "BuildingTimeTrackingRecords")
tasks: [RecordTask] @connection(name: "RecordTasks")
}
type RecordTask @model {
id: ID!
record: TimeTrackingRecord @connection(name: "RecordTasks")
task: Task @connection(name: "TaskRecords")
}App (.tsx)
import React, { useEffect, useState } from "react";
import "./App.css";
import { DataStore } from "@aws-amplify/datastore";
import { Task, TimeTrackingRecord, RecordTask } from "./models";
function App() {
const [recordTasks, setRecordTasks] = useState([] as RecordTask[]);
useEffect(() => {
queryRecordTasks();
return () => {};
}, []);
async function queryRecordTasks() {
const recordTasks = await DataStore.query(RecordTask);
setRecordTasks(recordTasks);
}
async function addRecordTask() {
const tasks = [];
for (let i = 0; i < 5; i++) {
const task = new Task({
name: `the task ${i + 1}`
});
await DataStore.save(task);
tasks.push(task);
}
const record = new TimeTrackingRecord({
hours: 2,
minutes: 30,
time: new Date().toISOString()
});
await DataStore.save(record);
for (const task of tasks) {
const recordTask = new RecordTask({
task,
record
});
await DataStore.save(recordTask);
}
await queryRecordTasks();
}
return (
<div className="App">
<header className="App-header">
<button onClick={addRecordTask}>Add</button>
<pre style={{ textAlign: "left" }}>
{JSON.stringify(recordTasks, null, 2)}
</pre>
</header>
</div>
);
}
export default App;I hope this helps, let us know how it goes.
moweex
ashika01
ghost
smithad15
ryanto
vrebo
cheunjm
samwightt
micstepper
PTaylour
kai-ten
sanyashvets
padunk
arabold
BrianMagus
ThomasRooney
Vazgen7788
salimdriai
amitchaudhary140
undefobj
svidgen
Which Category is your question related to? Datastore What AWS Services are you utilizing? AWS AppSync, Provide additional details e.g. code snippets We are implementing an RN application using AWS Amplify, we have a schema with a many to many relationships, as suggested we used a bridge model to link the tow models
Example Schema:
type Task @model { id:ID! name: String! icon: String records: [RecordTask] @connection(name: "TaskRecords") }
type TimeTrackingRecord @model { id: ID! hours: Int! minutes: Int! time: AWSDateTime! building: Building @connection(name: "BuildingTimeTrackingRecords") tasks: [RecordTask] @connection(name: "RecordTasks") }
type RecordTask @model { id: ID! record: TimeTrackingRecord @connection(name:"RecordTasks") task: Task @connection(name: "TaskRecords") }
Here RecordTask is used to link both Task & TimeTrackingRecord, we used amplify codegen models to generate models for us.
To complete our logic we are doing the following using datastore
1- Creating a set of Tasks 2- Creating a TimeTrackingRecord 3- loop over tasks and creating RecordTask
Then we tried two solutions:- 1- Updating already created TimeTrackingRecord to link it to the created RecordTask => Error on the update mutation by Appsync (no reason provided)
2- Relay that Datastore will connect the Tasks and TimeTrackingRecord, but unfortunately when we try to access TimeTrackingRecord tasks it is always empty however the RecordTask already created.
Any advice how can improve our M2M model to work fine with DataStore.