Michiel Dethmers

I don't understand the question. Quota on what? SQL queries, PHP commands? I'm afraid it's highly unlikely we can refactor the code to use fewer requests.

Actually, it probably makes sense to use ADODB for this. https://adodb.org/dokuwiki/doku.php?id=index They have some useful links: - https://adodb.org/dokuwiki/doku.php?id=v5:userguide:mysql_tutorial - https://adodb.org/dokuwiki/doku.php?id=v5:userguide:portable_sql -

I will start a WIP PR for the PostgresQL/ADOdb changes, marked for 3.7 and will see how far I get

Moodle seems to use ADOdb https://github.com/moodle/moodle/tree/master/lib/adodb But I'm interested to hear Duncan's opinion how to approach this.

You mean the transactional emails, as opposed to a campaign? Is there any reason why the bounce is not identified? Maybe it's better to fix that instead.

Maybe another option is Doctrine https://www.doctrine-project.org/projects/doctrine-orm/en/2.16/tutorials/getting-started.html

Ok. thanks. Yes, my initial primary objective is to support Postgres, and other DBs would be a bonus but not an aim. Yes, the PDO as you describe was the...

This is not as easy as it seems. Just initialising the DB structure already throws up enormous amounts of issues. One thing we need to do in a next version...

postgres doesn't like this in SQL, which phpList does all over the place - `where !confirmed`; # when using a tinyint/smallint as a boolean - `limit 0,50` # LIMIT #,#...

Also, we need to rename these columns as 'user' is a reserved word. - https://github.com/phpList/phplist3/blob/main/public_html/lists/admin/structure.php#L261 - https://github.com/phpList/phplist3/blob/main/public_html/lists/admin/structure.php#L272