Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZEo7-0006ou-QH for pgsql-interfaces@arkaria.postgresql.org; Wed, 10 Jan 2018 11:44:35 +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 1eZEo5-0006OO-IW for pgsql-interfaces@arkaria.postgresql.org; Wed, 10 Jan 2018 11:44:33 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eZEo5-0006OE-6T for pgsql-interfaces@lists.postgresql.org; Wed, 10 Jan 2018 11:44:33 +0000 Received: from mail-io0-x234.google.com ([2607:f8b0:4001:c06::234]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eZEo1-00010r-U0 for pgsql-interfaces@postgresql.org; Wed, 10 Jan 2018 11:44:31 +0000 Received: by mail-io0-x234.google.com with SMTP id c17so470451iod.1 for ; Wed, 10 Jan 2018 03:44:29 -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=oWDOKv2JQTLQx92GMPNYdhabJvnGEvLUNbKTwYD18to=; b=ULiVv4/RYjWiK8woUccCIIZ2qATpbKaoKNgLvw1e9kzxsxdJJWRfFyJpKLNQMokhQ5 bSV1j9FQT7+BSx7ZAc3IBXNw4z6GnbWlB10AxIEDi5nhassVuQeXFKdBzzuWMQGOI/7I P7jNZH1YWmGLziTe6wXLVqUqdtun0IQ59v9eVlajo2QvuvRZ7MSKtHOLsDSwov3vsfaN K7c4HMo4z5BBNpT0U/CMFrft6r+9404jtlTZMOMB0vzqBJ7PJHsd/1cf1o9fgxolhBfN 3Rg908gupZbfYaIhMTjhFj9FXnXTUNp8Wr5oK/8xe+FZ9Hc3TL6iLH+9VaBLqjOi//J6 e58g== 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=oWDOKv2JQTLQx92GMPNYdhabJvnGEvLUNbKTwYD18to=; b=qjW27rjPE4TIauIkwUNeaLANeC/a+0PymO3fRMPX4L6HSIJ/hN26kN5uSyh1jvYJJS jsenZqnGrXacty0BE3/7XeAIR3W0RKLQnDJaM4ev0T0jy9JVu9yZUeXDWrQt2zDxfQqI 8jbXU1Oz24Wz55rP6til3ffLU2DnWG1lSXQe2efhptkO/pdo7h8JzK2QNIt/F+7wl60t 6VCZLcLjxEBv5/Zi3UiSqu0s88Qxtv0dc25ddYJWcjpfYlMX+MdGINORloYZ8RFdDxcB VD3+incyBQTP8QnEuAX397lEhzTJY0OIzH2tkgNsy8tCVNPFHwus9PZdHoIds802ODJM gfMg== X-Gm-Message-State: AKGB3mKTidTcgeQPBuGvt7xQO161McTNMjp8WLJFChBJchpKYMp0yBn5 hjSYeuchAn/FmGklqZV0/TSEFHzWaoBj4RF8TRRj1w== X-Google-Smtp-Source: ACJfBosTzbGB2D5Mn7QX951X9v/x2uwQPxVAWjCM/mVH/xMOmeU9UwqDh72Vvh4qYi5ODRf9+yYXMLT73VPh75VGPsM= X-Received: by 10.107.50.3 with SMTP id y3mr17275253ioy.149.1515584666969; Wed, 10 Jan 2018 03:44:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.2.77.2 with HTTP; Wed, 10 Jan 2018 03:44:26 -0800 (PST) From: Ashutosh Sharma Date: Wed, 10 Jan 2018 17:14:26 +0530 Message-ID: Subject: Compatibility modes supported in ECPG To: pgsql-interfaces@postgresql.org Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi All, As per the documentation of ecpg, currently we support only two types of compatibility modes with ecpg and they are 1) INFORMIX and 2) INFORMIX_SE. However, it does accept any compatibility mode option that starts with INFORMIX*. For e.g. let us say, if i pass 'INFORMIX_BAD_COMPAT_MODE' as a compatibility mode, it still accepts it. [ashu@localhost bin]$ ./ecpg -C INFORMIX_BAD_COMPAT_MODE test_compat_modes.pc [ashu@localhost bin]$ Shouldn't we throw an error for this, instead of accepting it and assuming it as INFORMIX_SE mode. Thoughts? -- With Regards, Ashutosh Sharma EnterpriseDB:http://www.enterprisedb.com