HTTP PATCH - Weird Errors and Queries

[drveresh]

I have an EdgeFunction (EF) code that executes based on the request.method === "PATCH", and I am triggering the same PATCH type request via POSTMAN, but getting below weird console logs:

error 2024-08-20 17:26:23 (UTC+05:30) | 1:1 no such column: status
error 2024-08-20 17:26:23 (UTC+05:30) functions_replaceFunction - http://***:8090/v2/functions/myFunction?id=2798942&status=m
error 2024-08-20 17:26:23 (UTC+05:30) UPDATE functions SET 'id' = 'fn_liBvg3orbzDs', 'status' = 'm', 'options' = NULL WHERE id IS 'fn_liBvg3orbzDs' OR slug IS 'myFunction';

The POSTMAN endpoint looks like below, both with and without query params:

http://***:8090/v2/functions/myFunction?id=2798942&status=m
http://***:8090/v2/functions/myFunction <<with request body "{"id": 2798942,"status": "m"}">>

Below is the EF Code:

//let id = request.data?.id, status = request.data?.status; //When payload is part of request body
let id = request.params.id, status = request.params.status; //Via URL params set
let query = `UPDATE BadDomains set status='${status}' WHERE id=${id}`;
result = await connection.sql(query);
message = `Number of updates: ${result.length}`;

What is really going on here?

[TizianoT]

@drveresh

The PATCH method is not intended for edge function execution. It is used to create or update an edge function.

Executing
When executing an edge function, you should use either the GET or POST methods, depending on whether you need to include a request body.

The specific actions performed by the edge function are independent of the HTTP method used. The typical REST method conventions do not apply to edge functions in this context. You can think of an edge function as a piece of code that runs close to your database and can perform any operation you define. You trigger this code using a GET or POST request.

Within your edge function, you can access:

• Query parameters via request.params
• The request body via request.data

[drveresh]

Got it, thanks for the clarification. Please update the documentation accordingly, or else users will assume the same.