im personally hoping for some replica news, but we'll see
im personally hoping for some replica news, but we'll see
Invalid property: params => Expected array, received null (7400) seems to be coming from that validation. The params is an optional list argument that should only be provided if you have bind parameters in the SQL query.params === null be treated the same is not provided at all, since null is not a valid value per se for that list argument.When i changed the code to include a string array with params i started getting:Not sure what you mean here. Did you provide an empty slice?
All request parameters are wrapped in a generic Field type, which we use to distinguish zero values from null or omitted fields.
This prevents accidentally sending a zero value if you forget a required parameter, and enables explicitly sending null, false, '', or 0 on optional parameters. Any field not specified is not sent.
null is being sent for params. Did you not provide it at all (as your snippet above implies), or did you provide it explicitly as null?Invalid property: params => Expected array, received null (7400) is from that validation. That old version of the Go SDK I believe sends null when it should not send anything.nulls for now for these cases, but it needs some time to be rolled out.null for now so your original code should continue working once that's out everywhere.select * from sqlite_master; and see if the output contains the table you expect to be there.
--persist-to option? https://developers.cloudflare.com/d1/wrangler-commands/ and https://developers.cloudflare.com/workers/wrangler/commands/#d1:~:text=Minify%20the%20Worker.-,%2D%2Dpersist%2Dto,-stringwrangler d1 execute in my workers. Or maybe is it a config when I bind the like ENV.DB.execute?wrangler devbatch() but I cannot find any other resources than in this blog post.select * from sqlite_master;...
[[d1_databases]]
binding = "FIRESTORM_DB"
database_name = "firestorm-db"
database_id = "c020574a-5623-407b-be0c-cd192bab9545"
migrations_dir = "../d1/migrations" const findActivityStartTime = performance.now();
const activity = await prisma.activity.findFirst({
where: {
id: activityId,
goalId: goalId,
goal: {
userId: user.id,
},
},
});
const findActivityEndTime = performance.now();
console.log(
`Time to find activity: ${findActivityEndTime - findActivityStartTime}ms`
);batch()const id = this.env.MY_DURABLE_OBJECT.idFromName(teamId);
const stub = this.env.MY_DURABLE_OBJECT.get(id);