Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fiBeL-0007PU-FA for pgsql-interfaces@arkaria.postgresql.org; Wed, 25 Jul 2018 04:43:45 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fiBeJ-0001lq-Lt for pgsql-interfaces@arkaria.postgresql.org; Wed, 25 Jul 2018 04:43:43 +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.89) (envelope-from ) id 1fiBeJ-0001lF-Dy for pgsql-interfaces@lists.postgresql.org; Wed, 25 Jul 2018 04:43:43 +0000 Received: from mail-io0-x241.google.com ([2607:f8b0:4001:c06::241]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fiBeG-0008Kw-Ja for pgsql-interfaces@lists.postgresql.org; Wed, 25 Jul 2018 04:43:42 +0000 Received: by mail-io0-x241.google.com with SMTP id k16-v6so5274874iom.12 for ; Tue, 24 Jul 2018 21:43:40 -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:cc; bh=fPGRP1+S/+KiJA6ZUOjkRSP164nvftgmsG4VMmyjTQA=; b=MhgUQmGG9UKsanh6QV7CSC4EZpJCcgl4m+p9d0lTa0mOSl/L7jWkn70hO8RT+GHowe bk/VXFbzKbK+sWvJkgeVNlpo9142eXfX0fmJDmcemilgHhKxaxjAv4j46fnHyBWGquKv v64ekh48nf863Wv9w9nZoVei6naObMitROjjfz6S0XxLPFeQiLKMaK5goudOwH8d00cG 5eQReJrenrIhScsVd+RPVBx6+4muX5GQsWRvKwnnVbv2fjE3jm+KhVr8beU3mFYIMwvq Zg5C2o5VbfNJwTuusNyPObUZEpzR9enfspl4tvUPBj8B72X4meDIsgqhWvRYnTDB+7yU STLA== 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:cc; bh=fPGRP1+S/+KiJA6ZUOjkRSP164nvftgmsG4VMmyjTQA=; b=im801hagUNXvCRdMhX2W7zsF9eVOxzcQRZZwss97pSNkZY2YpzcLv6DkOMmc2aBNfL 4h1atUhDXKe+3xq8aZKqaHLEQFBLawQA1y92OGpacJSgUilqdFySOnsRo1cVbWgrQhJI IPKS21v3zPhqp84Kf4bTpkSng2vrkpVZo/gnVD9x1JIH6mN89bokZbvra/J74gRSfdvv DCT5JasdRyKP3gzBkVzupSvgsZ2VVI0FKLsRT6cnz7RrqAEUzH9gAMvONBM8cUSqZOTx P6rQCONBtzF0H4nSay8O4fH8A02822zWKKYoRK65NGeOMcKb5CdkPqyIZD18X+KwaF9C MnlA== X-Gm-Message-State: AOUpUlGO855L3bXLEHjckvmSIGbvMGKW+H4LNmcB7imrYDSQN7AVUhgL PTS4Uxo6E5CUWW9pFmY5JkZBZU7dM1lfXEeHax/7v/o0 X-Google-Smtp-Source: AAOMgpd65EpdomisrHwPtTbUEX5Au0HIGWt9a2D+cmxltmRiX55ZcM3+3eERBtJGIfFP4Msik1u9ridaNG0C3dBZH94= X-Received: by 2002:a6b:1502:: with SMTP id 2-v6mr16517082iov.203.1532493818500; Tue, 24 Jul 2018 21:43:38 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:5989:0:0:0:0:0 with HTTP; Tue, 24 Jul 2018 21:43:38 -0700 (PDT) From: Ashutosh Sharma Date: Wed, 25 Jul 2018 10:13:38 +0530 Message-ID: Subject: ECPG: New compatibility mode is case sensitive To: pgsql-interfaces@lists.postgresql.org Cc: Michael Meskes Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, While trying to explore on a new compatibility mode (ORACLE mode) in ecpg, I could see that for ORACLE mode we do case sensitive comparison (using strncmp) whereas for other two modes we do case independent comparison(using pg_strcasecmp) which means if user is trying to compile ecpg application in oracle mode, he/she will have to take care of the cases but, that's not true for informix or informix_se modes. How about doing case-independent comparison for ORACLE mode as well.? Please have a look at the following examples for details [ashu@localhost bin]$ ./ecpg -C oracle test.pc Try "./ecpg --help" for more information. [ashu@localhost bin]$ ./ecpg -C INFORMIX test.pc [ashu@localhost bin]$ ./ecpg -C informix test.pc -- With Regards, Ashutosh Sharma EnterpriseDB:http://www.enterprisedb.com