Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:96616 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 18818 invoked from network); 26 Oct 2016 15:57:15 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Oct 2016 15:57:15 -0000 Authentication-Results: pb1.pair.com header.from=adambaratz@php.net; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=adam.baratz@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.44 as permitted sender) X-PHP-List-Original-Sender: adam.baratz@gmail.com X-Host-Fingerprint: 209.85.214.44 mail-it0-f44.google.com Received: from [209.85.214.44] ([209.85.214.44:37357] helo=mail-it0-f44.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 84/4B-24108-A52D0185 for ; Wed, 26 Oct 2016 11:57:15 -0400 Received: by mail-it0-f44.google.com with SMTP id u205so41370116itc.0 for ; Wed, 26 Oct 2016 08:57:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=kWShr7j8KQBH8/4GOouTd+aUO6l8CE8r6I6SuFt46D8=; b=OOsS3p6CU3BXQqgUGmb4nROttZ2hazOoPFo+QZ0Epw7f2l8wG1u/jxaac+fHaH+4+Q 0b/2yaBS/HCZ6YngF7EmSupK4hgoybGnU4LDT1cT5vYI3q/CDoaMcSK/T1qHF2eVFwM5 seOwNUSd3G1qkCcx4WwInU2A5FpZKJnuBNpHd1bGIk8Ab8nsTYYNdRuMulEUA375D/72 UVdaNygWDtrEUu3t9yG1fc89gzYVp0BCkhJ8A+Q6ACzaCvpd5hjwmrpc3PN5+nBBk0Yo svcPAwGscsCuiO2IPRT9FBW8Ecs9J5d0dKKzoxeFTuVPY0ZVJg+Lhbj5JvFp+ovFn4Ls TEVw== X-Gm-Message-State: ABUngvdZLRFrhdx+0yqMi0u975dMxtz282SGC0Bt2iXVyythvOS+TTlI++uSRtQMJwNxrA== X-Received: by 10.36.57.5 with SMTP id l5mr6828572ita.26.1477497431765; Wed, 26 Oct 2016 08:57:11 -0700 (PDT) Received: from mail-it0-f48.google.com (mail-it0-f48.google.com. [209.85.214.48]) by smtp.gmail.com with ESMTPSA id 80sm1197625iot.36.2016.10.26.08.57.11 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Oct 2016 08:57:11 -0700 (PDT) Received: by mail-it0-f48.google.com with SMTP id e187so29851384itc.0 for ; Wed, 26 Oct 2016 08:57:11 -0700 (PDT) X-Received: by 10.36.54.69 with SMTP id l66mr6784641itl.3.1477497371521; Wed, 26 Oct 2016 08:56:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.158.164 with HTTP; Wed, 26 Oct 2016 08:56:10 -0700 (PDT) In-Reply-To: References: Date: Wed, 26 Oct 2016 11:56:10 -0400 X-Gmail-Original-Message-ID: Message-ID: To: Lester Caine Cc: "internals@lists.php.net" Content-Type: multipart/alternative; boundary=001a1143d5befca68c053fc6a957 Subject: Re: [PHP-DEV] Re: [RFC] Debugging PDO Prepared Statement Emulation From: adambaratz@php.net (Adam Baratz) --001a1143d5befca68c053fc6a957 Content-Type: text/plain; charset=UTF-8 > > Since PDO is an interface to third party databases this seems totally > out of place in PHP. Prepared statements are a sensible mechanism for > for anyone wanting secure access to those database, so what is the point > of this code. I don't want to solve for database access. I want to create a testing tool for emulated prepared statements. We already have PDOStatement::debugDumpParams() for revealing some PDO internals. This would offer another slice. I don't want to create another path for talking to the database. I updated the RFC introduction to make this clearer. I also added a description of another use case (.phpt tests). Older mysql did not have prepared queries hence the default of > converting the more secure SQL into something old mysql could handle. I > presume that dblib has the same fundamental problem? But mssql has > prepared statements so dblib SHOULD provide that interface? > MSSQL understands prepared statements, but not through DB-Library. The API dates back to the early '80s. It's really quite primitive. ODBC is the "right" way to use prepared statements with MSSQL, but it's honestly not a drop-in replacement. --001a1143d5befca68c053fc6a957--