Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113201 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 48728 invoked from network); 18 Feb 2021 01:10:32 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Feb 2021 01:10:32 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 699B21804B3 for ; Wed, 17 Feb 2021 16:57:39 -0800 (PST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,HTML_MESSAGE, RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 17 Feb 2021 16:57:38 -0800 (PST) Received: by mail-wr1-f51.google.com with SMTP id t15so716931wrx.13 for ; Wed, 17 Feb 2021 16:57:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=z/pt26r1nYKD66jpzWFeWKt8e+ZBxJqqbuVIDgkbKGI=; b=TnBKrIzjpupw7C7u4JeSiwD/yb9hdWD3Z3fRzV4+Wc7h2YH6a/mLAoiv2T3HJoV7r7 QlTfX6XWi8cQpq4t9GCJAgfPQwgKCXNoj1GhOPAD2rUEDtqi5gL0mzMBj5kYuTm8iTBU z14/s8fIKgOxILhAY88p4Zlb5h5DnB5Zq3SfmphAnG5CdVp4ygGRIxum7AD8wGy6k2wK gvBDrnM3d6iMqSY+KPEk2QO1RdqoZ9OqChNnSLRLG9u+7ryKjgcBMhndY1pP62F8uoDl Mh6xDW9jr+hRUB2RqjitmQRHwqSs4PkHs2a6sxgTvj1JAVKf6wX8b7JJjS9uRSEG4hcP NG3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=z/pt26r1nYKD66jpzWFeWKt8e+ZBxJqqbuVIDgkbKGI=; b=k9kz32M3xDyPPRBersg3DSZLiBAOBphLuVGOdVN0J8olwSs45amokrv1G5OcMcPxDP w2YeEOFv+NlymUvtnf1WTlYrGbFimTEqMOZGtCYMA0SID6Bg45VAGbFjxxXodTyuup9k 8IOjg1ihCCgssHXYoHPv+ktdX1BNOi3qPPShFoDJ4RoyK9cdGOgrckuhfDx+MebiUewB 4CCI/M4PFPoYb17eplMDSepWOoi68W2e1/+b+8phwaDc+NgdLbvfZE9H1ofxl0r3LwQA HEPsfH8YW8A5aZ4UyV3u/g4suA1Y5wrfvPbrf7j91KridcT69Y+/jbnr5dADVAzxZRiy Hraw== X-Gm-Message-State: AOAM5332SmgyxwXO4LJ0GWA87lpiCV3US+D7Cabte2BT1cAbv4Eh0xvr fOsB7Mi/8uucI7xnt54p40lvawRC7BkCSC6IAy704WRMSDP0 X-Google-Smtp-Source: ABdhPJyrCKBzBw6BwdVusLIP0cmclGrnPFUfgsRrSpK61TWb6JQwZZ1HD1J4os2L0Ws8fFopmrKjznV4Kv8RF4XpZms= X-Received: by 2002:adf:9226:: with SMTP id 35mr1740765wrj.408.1613609855117; Wed, 17 Feb 2021 16:57:35 -0800 (PST) MIME-Version: 1.0 Date: Wed, 17 Feb 2021 16:57:24 -0800 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000386c9405bb91d26c" Subject: Potential RFC around PDO From: dbeardsl@gmail.com (Daniel Beardsley) --000000000000386c9405bb91d26c Content-Type: text/plain; charset="UTF-8" wiki username: danielbeardsley === Background I was told to introduce myself. I've been in software development for more than 20 years and have been working with php for 10 or so of that. I've only had a little contact with this group, but I've got at least one past pull merged on the php-src repo: https://github.com/php/php-src/pull/271. At iFixit we use a forked version of php with a small change to allow automatically html-escaping echoed strings: https://github.com/iFixit/php-src/commit/cb6eb5c35a07c843e5b357884186d77e3a1a2981 . It's not something this list would be interested in as it's rather special-purpose, but I'm mentioning it to show I'm somewhat familiar with the php build system. === Why I'm emailing now: I've opened a pull request on php-src: https://github.com/php/php-src/pull/6677 and I've been advised to make an RFC. The first step is emailing! I'd like to propose adding a function to the mysql pdo driver (in the same way postgres and sqlite have) to extract the count of warnings from the last executed statement. See the pull request linked above for a more thorough description. Should I make an RFC out of this? Thanks for your time! Daniel Beardsley --000000000000386c9405bb91d26c--