I suggest adding new methods to SQL queries.

[korenevskiy]

// $query = Factory::getContainer()->get(DatabaseInterface::class)->getQuery();
$query->selectQ($columns);
$query->whereQ($conditions);

I propose new functions similar to the existing ones but with the suffix Q.
The task of the new methods is to wrap the names of columns and rows in the necessary quotation marks.
I always write queries as strings, ignoring the methods of the Query class. The reason for this is the difficulty of reading, the difficulty of perception, the difficulty of writing.
I suggest separating the processing of quotation marks from the business logic.
You and I must agree on the best syntax. So that the new methods take into account the needs of 80%-90% of all requests.
The new methods will wrap columns and row values in the appropriate quotation marks inside themselves.

$query->select($query->qn('name'));
//similar to
$query->selectQ('name');

$query->where($query->qn('name').' = '.$query->q($name));
//similar to
$query->whereQ('name',' = ',$name);

The new method will wrap the first parameter in ` quotes. Take the second parameter as a comparison. The third parameter will be wrapped in direct " quotation marks.
I am sure that my colleagues will offer a more convenient option, with support for arrays.
But I'm sure that in 90%-95% of cases we use simple queries, in 99% of cases people reread their code, stumbling over the complexity of writing queries in PHP joomla.
We can also add new parameters to existing methods, taking into account the format of the methods.

$query->select('name', true);

$query->where('name',' = ',$name);

Let's discuss your best options.

[korenevskiy]

Hello @Fedik . Sorry to disturb I was afraid of getting a negative review without any reason or explanation. That's why I wanted to know your opinion on this issue.

[Fedik]

It is not that simple, the select/where query can be complex.
And if we add selectQ, whereQ then developers will assume that it will quote complex pattern also, but it will be hard to implement.

In short:

• it is not a good pattern.
• it does not solve any real problem, but may add a few new.

[korenevskiy]

In short:

* it is not a good pattern.

* it does not solve any real problem, but may add a few new.

I thought that code readability and simplicity of functionality were among the ideologies of Joomla.
Can you recommend your vision?
Of course, this does not affect the actual operation of the extension. But this is related to the development and support of the extension. Maybe you can recommend another supervisor who was directly involved in the database framework.