Closed jamiewhths closed 3 months ago
Noting that this implementation uses the getRecord API call to check if the recordId already exists. If tables are wide, I imagine it may be significantly more efficient to do a table query for the id column with a limit of 1 instead? This could be tested in the future. If that is desirable I can add an issue to the backlog.
@nickdickinson Because of the way we implement queries, getRecord()
will always be faster.
From AI-3942 Resolved by commit: 2b4bcf6