Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:110578 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 96436 invoked from network); 16 Jun 2020 11:47:14 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 16 Jun 2020 11:47:14 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id D623F1804C7 for ; Tue, 16 Jun 2020 03:32:38 -0700 (PDT) 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.2 required=5.0 tests=BAYES_40,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-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-io1-f51.google.com (mail-io1-f51.google.com [209.85.166.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 ; Tue, 16 Jun 2020 03:32:38 -0700 (PDT) Received: by mail-io1-f51.google.com with SMTP id o5so21258192iow.8 for ; Tue, 16 Jun 2020 03:32:38 -0700 (PDT) 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=kf4F+rSGFTFqASsJFoXWi6H3NYiYCv6H1QA0ROa/HBw=; b=Oq8Oqg72TzmWaP7bx4bJ0PvhqeyExl/Dky2HLJk2kBqAUH70WMVU5FyUhurKvT1pqK R3wh/X9W+u9xVjqtrvQSrWdNPT6p4aHhUJzGzmsugtSHC3eI1JwHTpb4iyxQBfokJvMa gNSAdLWZoZAYCqM/RDMU/Gx1kTtpgJRca/29bhZOz74XfOffs8/tag9dNtVS4vAY3Y9k u9RI2TWEvF97wcGqDXvfQWvsBZtmzyktSezFtMkXIFAKl9g47pKbxohjuLLMoahIBu2n E8Wnphc8edfx4vmvmoTlR+NAPyFRf5le0+3EqwEZelc6OfEFI4gXngferG8eAFcnzu3p 8PgQ== 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=kf4F+rSGFTFqASsJFoXWi6H3NYiYCv6H1QA0ROa/HBw=; b=Kf9z2SG7XVuGKNOZVIf3dp+6fBlf/L3xSqSBHdhRuF5aX67/W+rRelzufvwRF/b5iq z7LFgUxMlujMLihARz1K/Vbiam1j6kmIsrcLItHjUSZTBqfODLsV7TWoiL0zR1vfvwc+ w7WgwRfoYAMYQcYYKXUpsPJ0RaVhuiIcrV+cVt3qFSuVkG9xsHjhjy7Ilp5GxxJCKVYP JvaRh7pJpdQaWu5/ZkzQjb5nAP+/QqYKNNS0OTJ9+PitdARwfquCoHgPes1P5SFBswxT GnbxN3H2R8cIUlL1jsebMF1Je3f9ezbe0FXSWtQuRJ7F3fdZRwB7hScJdrc3yVY1zKdu 7VPQ== X-Gm-Message-State: AOAM531jOhun+z26AlrWrzwM05KRAZgP9ldwlTfdVAA0+hGZ5eSvaH33 JIUVUiWjlj+bJewqRkBkeq0OPWrb X-Google-Smtp-Source: ABdhPJwnLJkXTU1m2NDYMEcan8xQ37e74ytMxZGONsA++MK37TIQ3lMB6VODXAvYIVLqZFYc82tNyg== X-Received: by 2002:a05:6602:2c8f:: with SMTP id i15mr1935067iow.45.1592303557809; Tue, 16 Jun 2020 03:32:37 -0700 (PDT) Received: from mail-il1-f176.google.com (mail-il1-f176.google.com. [209.85.166.176]) by smtp.gmail.com with ESMTPSA id j80sm9915325ili.65.2020.06.16.03.32.37 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jun 2020 03:32:37 -0700 (PDT) Received: by mail-il1-f176.google.com with SMTP id j19so14124182ilk.9 for ; Tue, 16 Jun 2020 03:32:37 -0700 (PDT) X-Received: by 2002:a05:6e02:10e:: with SMTP id t14mr2218189ilm.97.1592303557052; Tue, 16 Jun 2020 03:32:37 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 16 Jun 2020 11:32:01 +0100 X-Gmail-Original-Message-ID: Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="000000000000e4a9d305a8310f5b" Subject: SQLite3, PDO/SQLite and driver specific methods From: phpmailinglists@gmail.com (Peter Bowyer) --000000000000e4a9d305a8310f5b Content-Type: text/plain; charset="UTF-8" Hi list, 4 months ago there was a discussion about the future of SQLite3 and PDO/SQLite extensions (https://externals.io/message/108256), highlighting the effort required to maintain two codebases. Recently I encountered https://bugs.php.net/bug.php?id=64810 and thence https://github.com/php/php-src/pull/3368. In the pull request Christoph M. Becker wrote on 8 May: This PR is still unresolved. The problem is that adding driver specific > methods to PDO via the currently existing mechanism (basicall `__call` > like), has faced some strong oposition, so this should be discussed on > internals. It probably would make sense to start some general discussion > about this issue, and to hopefully come to a solution, so driver specific > functionality could be added to PDO in the future. > [Link: https://github.com/php/php-src/pull/3368#issuecomment-625731098] In light of this comment, I'm emailing the list to start a general discussion about this issue. As alluded to earlier, there is a maintenance burden, and for users the lack of parity between the two extensions can be an issue. PDO is well established as providing a standardised access layer across databases. SQLite requires extensions to be loaded to gain feature parity with other databases (e.g. to load geospatial functions) and since it is not a database server these have to be loaded at runtime. PDO has three sqlite-prefixed functions (https://www.php.net/manual/en/ref.pdo-sqlite.php) but not one to load extensions. Is it a problem to add one? If it is, how can we change and improve the current situation? Peter --000000000000e4a9d305a8310f5b--