Can SQL statement splicing support placeholder rules other than question marks? about gf

[Issues-translate-bot]

Bot detected the issue body's language is not English, translate it automatically. 👯👭🏻🧑‍🤝‍🧑👫🧑🏿‍🤝‍🧑🏻👩🏾‍🤝‍👨🏿👬🏿

---

Is your feature request related to a problem? Please describe.

1. Sometimes the sql statement originally contains the question mark character, but after using db.query, the question mark that does not want to be escaped will be replaced, causing sql execution errors;
2. In addition, during the sql filling process, a value may be filled repeatedly in multiple places. Using question marks as placeholders will cause many repeated values ​​​​in the input parameters. The input parameters will be very long and it is easy to make wrong rows;
3. It is expected that the injection of SQL can be allowed in the custom SQL. It is hoped that the table to be queried by the SQL can be added through placeholders. Currently, it can only be processed through character splicing, and the custom statement processing will be very fragmented. If you are worried about SQL injection, direct string concatenation is unavoidable.
   Describe the solution you'd like
   I hope there is a method similar to Java that uses ${} #{} placeholders to splice complete statements, and you can choose whether to add quotation marks to the fill parameters.

Describe alternatives you've considered
Or you can add corresponding interfaces to allow customization of relevant injection rules.

Additional