Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZIUN-0001Ev-VX for pgsql-interfaces@arkaria.postgresql.org; Wed, 10 Jan 2018 15:40:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZIUN-0004SP-9P for pgsql-interfaces@arkaria.postgresql.org; Wed, 10 Jan 2018 15:40:27 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eZIUM-0004SF-Vk for pgsql-interfaces@lists.postgresql.org; Wed, 10 Jan 2018 15:40:27 +0000 Received: from mail-it0-x242.google.com ([2607:f8b0:4001:c0b::242]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eZIUI-0003RX-Va for pgsql-interfaces@postgresql.org; Wed, 10 Jan 2018 15:40:26 +0000 Received: by mail-it0-x242.google.com with SMTP id f143so16688446itb.0 for ; Wed, 10 Jan 2018 07:40:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-transfer-encoding; bh=wvAsOzJUGFly4KP6kMSCsZ5jAJ8FMHiJcfJoOcNC7Gs=; b=rZMP/Oa52u0IeH9Cw1wdBuy4BWNa2Db7sqCAnhZNtzNGJsodqdWy4rCN9SrKWG1pdQ Hk3msLWsTzSmJRWQOfL73DLU65PbYVmlkcd+VG6DOwnebeH6RAKrEj4Ei0xGyMqho+23 4X1Aa8rc4D2hw0Lp+wvXmhOBzL9EG/y8nLy1Mw3LodgqB6DtjQfBTwHTVlqITwPCH11A x4/e75r5dDMQpKiEVQrs+ehK6U7RcNsRgzTHmNeI+XbYh19FYKkRkwx1wEOuAkzSrJ0r rAgfgTROBgp8PcaT7xLB9pKGRnkOYJAGd5+TAgU/v3G3tN+49eX/FzkUpx08w41NRRTb Z+Hw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-transfer-encoding; bh=wvAsOzJUGFly4KP6kMSCsZ5jAJ8FMHiJcfJoOcNC7Gs=; b=Q21JmVCAqyLVu2/3Up1OTgXnT7puZcMFdzy7mlEcoKOEapZ6aq79qmHu+pYAqAx5oI oL9xcoLLj/Gdugj81SjyJ+Ki1wRfxfBEu6XuXygoAoL/pEAYrKi9EmdE8NB58piYxJkH JUD3E1xwlSYX8rBr0mljWS8ice9OpoetAgNH0YcI3dMRAqW6OPi87JVgOpCps7xJT5+g zMqnZ2qOr8qlrqUZ92HZMctaNXExsfwcsAB69oY9u+F9GfoJ4NYmrmNvIKNklV8+alky gj1moIR09U/p5w/zJhVcSE5BCzpz0j5UV3/xRqPlgOFTu8nvobEImVsM74fLgBTlRKAk IEZA== X-Gm-Message-State: AKGB3mJJ3AxBbfOsubzIAwei9myyxZhHfMoIGe6eVnrfb2YMhE1Z15kq tQ91y2rHCwXUyQYZubsMSXsjR1Cq+s5MB+K41SM= X-Google-Smtp-Source: ACJfBou9SptKHQy34FZVkwOMyyCfQX3cJ1mE3FFBo0o1uqnbcEAHdTAuxbUsBBsPqT/Vgu8NIHPjovNh/8HJrTkC5pI= X-Received: by 10.36.155.197 with SMTP id o188mr18260802itd.84.1515598820728; Wed, 10 Jan 2018 07:40:20 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.77.2 with HTTP; Wed, 10 Jan 2018 07:40:20 -0800 (PST) In-Reply-To: <20180110122916.GA1160@feivel> References: <20180110122916.GA1160@feivel> From: Ashutosh Sharma Date: Wed, 10 Jan 2018 21:10:20 +0530 Message-ID: Subject: Re: Compatibility modes supported in ECPG To: Ashutosh Sharma , pgsql-interfaces@postgresql.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Wed, Jan 10, 2018 at 5:59 PM, Michael Meskes wro= te: > Hi, > >> Shouldn't we throw an error for this, instead of accepting it and >> assuming it as INFORMIX_SE mode. Thoughts? > > Yes, I'd say that would be better. :) > Thanks Michael. Shall i submit a patch for it. Also, what about making the compatibility modes case insensitive. Currently, ecpg accepts compatibility mode only in capital letters. In case if the INFORMIX or INFORMIX_SE is entered in small or mixed type letter, ecpg throws an error. Shouldn't that be handled as well? -- With Regards, Ashutosh Sharma EnterpriseDB:http://www.enterprisedb.com > Michael > -- > Michael Meskes > Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) > Meskes at (Debian|Postgresql) dot Org > Jabber: michael at xmpp dot meskes dot org > VfL Borussia! For=C3=A7a Bar=C3=A7a! Go SF 49ers! Use Debian GNU/Linux, P= ostgreSQL