More developer-friendly, intuitive way to updateDocument

[zdanl]

Hello,

Not all of my inquiries in Discord are needed, sometimes it's just a matter of disregarding the obvious and seeing the bigger picture of the backend solution. This one, is very realistic.

The Patch

Story

I wrote an API in NodeJS last night, which interacts with an Appwrite Database.
It's a bit of a mess, since NodeJS and not Typescript or Nest. Also everything in one file

I am truly convinced of Appwrite, and its use as the Backend for all my stuff, small apps and big enterprise.
Sometimes, its limitations are uncomfortable, and sometimes blocking.

The reason for last nights API was the creation of Developer API Keys for the App/Platform I am building on Appwrite.
Such things require API Keys. Also 2FA via Authenticator.

I was told not to merge more than one issue per ticket, so I'll just share my suggestion with regards to its value to you.

The Problem

sdk.documents.updateDocument('appwrite', 'logs', 'efniufn24323bd', {
    'last_action': 'api_key_creation'
});

Value Proposition

1. Generally you don't have the Document ID. Period.
2. A comfortable hack

try {
    sdk.documents.updateDocument('appwrite', 'logs', {
        'api_key': '...',
    }. {
        'last_action': 'api_key_creation'
    });
}.catch(err) {
   res.send('api key doesn't exist');
});

vs.

    // only producing documents belonging to the active user
    const resp = await sdk.documents.listDocuments('appwrite', 'logs');

    // uncessary code and typing
    if (resp.amount > 0)  ...() => { ... resp.documents; // somehow getting the document id }

    // and once more
    sdk.documents.updateDocument('appwrite', 'logs', 'that document id', {
        'last_action': '...',
    });

Implemetation

Generally speaking, the MariaDB Statement is a SELECT looking for _uid (the Document ID). What would be needed to resolve the
issue of invoking a dynamic array of queries instead, is a INNER JOIN into the WHERE clause. The code base in question is the Utopia Framework, Database Module. https://github.com/utopia-php/database This solution would look roughly like this:

More generalized speaking, a correct example of an INNER JOIN, gratuity of GPT4 (cause I couldn't remember the INNER)

Kindly, if you select 'Not at all', reply to this post with a different solution other than listDocuments to obtain one specific document, in any real world scenario.

This will be implemented correctly one way or another, it's very little work from here on. I would just like to know if it can be Pull Request'ed into Upstream or remains in a Fork, priority wise. I can see no reason why it wouldn't be merged, if coded correctly and without room for the JOINT statement ruining the original query. Utopia Database definitely already has a Query Builder for this, there just is no updateDocumentBy function it seems.

@stnguyen90 @eldadfux

[zdanl]

FYI Elasticsearch does it.