You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SELECT srvname, srvowner, srvfdw
FROM pg_foreign_server;
Or
SELECT um.user_mapping_oid, um.srvname, um.usename, um.umoptions
FROM pg_user_mappings um
JOIN pg_foreign_server fs ON um.srvname = fs.srvname
WHERE fs.srvname = 'your_foreign_server_name';
(from ChatGPT, not tested)
Implementation
Within /twenty-server/src/metadata we will create a new folder remote-server folder similar to what was done in the object-metadata folder. In the latter we've used nestjs/graphql query to auto-generate mutations but this won't be helpful here, we'll want to overwrite/create our one mutation for create/update/delete/read (the same way we've overriden deleteOneObject already)
Unlike Postgres we should consider that 1 server = 1 user mapping.
So for example in the create method we would do 3 things:
Create the remoteServer record in our metadata schema
Create the SERVER (Postgres function)
Create the USER MAPPING (Postgres function)
The text was updated successfully, but these errors were encountered:
Context
Once we have completed #3742 we now need to create a proper API to manipulate remote servers.
Reference
For create/update/delete:
For read:
Or
(from ChatGPT, not tested)
Implementation
Within
/twenty-server/src/metadata
we will create a new folderremote-server
folder similar to what was done in theobject-metadata
folder. In the latter we've usednestjs/graphql
query to auto-generate mutations but this won't be helpful here, we'll want to overwrite/create our one mutation for create/update/delete/read (the same way we've overridendeleteOneObject
already)Unlike Postgres we should consider that 1 server = 1 user mapping.
So for example in the create method we would do 3 things:
metadata
schemaThe text was updated successfully, but these errors were encountered: