prisma1
prisma1 copied to clipboard
prisma
add createMany mutation
Feature Request
A createManyXs mutation to create many nodes in a batched fashion.
Suggested API:
mutation {
createManyItems(data: [{
name: "Tesla"
price: "1000"
}, {
name: "Audi"
price: "2"
}]) {
ids # list of ids for newly created nodes
count
}
}
Where would i look in order to implement this?
After all, most of the groundwork for this seems done and things like TypeCreateManyInput already exist when you create nested resources.
I tried to find "CreateManyInput" via code search, but turned up empty-handed. Not sure if i was even searching the right repo.
Are there plans to tackle this any time soon? Or at least some help from the prima team as to how it should be tackled for contributors to work on this?
Hey guys! This looks pretty simple to implement since Prisma already have updateMany. What are the blockers?
one of the first thing I am using prisma is the bulk import of csv rows, so bit saddened by unpresence of this feature
does anyone have a good workaround for this?
It isn't pretty but I'm temporarily getting around it by building a dynamic template string that prepends an arbitrary unique ID to each data object getting inserted and calling the mutation method. Using axios for the POST, It looks something like this:
const players = [{id: 'a', name: 'playerA'}, {id: 'b', name: 'playerB'}]
let playerMutations = ``;
players.forEach(player => {
playerMutations += `
p_${player.id}: createPlayer (
data: {
name: "${player.name}"
}
) {
name
}
`;
});
const mutation = `
mutation {
${playerMutations}
}
`;
try {
await axios({
url: 'http://localhost:4000/default/dev',
method: 'post',
data: { query: mutation }
});
} catch (e) {
console.error('Error in PlayerServices run:', e.message);
return [];
}
@vladimirvolek @HugoLiconV @gotexis @george1028 @rollrodrig check out my comment above. temp solution that im currently using
You can use raw access (edit prisma config rawAccess: true). This option provides $graphql function where you can insert many values in a single request.
docker-compose.yml
PRISMA_CONFIG: |
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
databases:
default:
connector: mysql
host: mysql
user: root
password: prisma
port: 3306
rawAccess: true // HERE
migrations: true
generated/prisma-client/index
export interface Prisma {
$exists: Exists;
$graphql: <T = any>(
query: string,
variables?: { [key: string]: any }
) => Promise<T>;
example
await prisma.$graphql(`
mutation {
executeRaw(
query: "insert into \"default$default\".\"Address\" (\"address\", \"createdAt\", \"id\", \"updatedAt\") values ('00:01:cc:00:00:02', '2018-10-26T08:51:04.242Z', 'MDA6MDE6Y2M6MDA6MDA6MDIwMD', '2018-10-26T08:51:04.242Z')"
)
}
`);
more info https://www.prisma.io/forum/t/how-i-can-create-many-records-at-the-same-time-with-the-prisma-client/4723/5 https://github.com/prisma/prisma/issues/3300#issuecomment-430696015
@vladimirvolek What about SQL injection while using the raw queries? Is prisma already handling it or should we implement it by ourself?
@sapkra In this case you probably need to handle it yourself since Prisma is not aware of the semantics of the query you are dynamically building.
It has been well over a year at this point, is there any dialogue on this?
u can do something like this 😉
@ahmedB7r , that works when it's only a few items. But if someone is attempting to add > 1000 items, Prisma will begin rejecting the requests after the queue reaches 1000 to protect the database. A feature like createMany would allow Prisma to internally queue these requests and handle them as it sees fit with the possibility of providing updates as the queue is worked to completion.
Does this mean the team won't work on Prisma anymore? Now that Prisma2 is taking all of their attention?
