From: Ryan Mooney <ryan@pcslink.com>
To: pgsql-interfaces@postgresql.org
Cc: pgsql-bugs@postgresql.org
Subject: Re: [INTERFACES] ECPG Connect user :variable problem
Date: Wed, 20 Aug 2003 08:05:28 -1000
Message-ID: <20030820180528.GA89815@pcslink.com> (raw)
In-Reply-To: <20030819221656.GA10232@pcslink.com>
References: <20030819221656.GA10232@pcslink.com>
Sorry about that last patch, I hit the wrong one (my bison is
way out of date, so I'm hacking the resulting .c file for test
and backporting to the .y file, not that thats an excuse :)
Anyway here is a patch to 7.4b1 that seems to apply to the snap
from yesterday as well.
This allows you to
EXEC SQL CONNECT TO :target as :connection_name user :uname using :password;
and have the uname and password C variables get passed correctly to the
ECPGconnect fucntion after epgc processing.
On Tue, Aug 19, 2003 at 12:17:08PM -1000, Ryan Mooney wrote:
>
> Hello,
>
> I'm having a major problem using ecpg with 7.4beta1. The problem is that
> if I try to pass in the username or password as :variables to the EXEC SQL
> CONNECT code they are essentially ignored (replaced by " ?").
>
> I've tried it on both redhat 7.2 IA64 and Redhat 9.0 IA32 (different enough
> that I don't think its the platform). I also tried it with postgres 7.3.2
> which seemed to do the "right thing" and put the variables into the ECPGconnect
> call.
>
> Any thoughts?
>
> ------------------------------<snip "connect.pgc">---------------------------------
> int pg_connect(void)
> {
>
> EXEC SQL BEGIN DECLARE SECTION;
> char *target = "dbname";
> char *connection_name = "myconnection";
> char *uname = "myuser";
> char *password = "mypassword";
> EXEC SQL END DECLARE SECTION;
>
> EXEC SQL CONNECT TO :target as :connection_name user :uname using :password;
>
> }
>
> ------------------------------<snip "connect.c">---------------------------------
>
> int pg_connect(void)
> {
>
> /* exec sql begin declare section */
>
>
>
>
>
> #line 5 "connect.pgc"
> char * target = "dbname" ;
>
> #line 6 "connect.pgc"
> char * connection_name = "myconnection" ;
>
> #line 7 "connect.pgc"
> char * uname = "myuser" ;
>
> #line 8 "connect.pgc"
> char * password = "mypassword" ;
> /* exec sql end declare section */
> #line 9 "connect.pgc"
>
>
> { ECPGconnect(__LINE__, 0, target , " ?" , " ?" , connection_name, 0); }
> #line 11 "connect.pgc"
>
>
> }
>
>
> --
> >-=-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-=-<
> Ryan Mooney ryan@pcslink.com
> <-=-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-=->
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html
--
>-=-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-=-<
Ryan Mooney ryan@pcslink.com
<-=-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-=->
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: ryan@pcslink.com, pgsql-bugs@postgresql.org
Subject: Re: [INTERFACES] ECPG Connect user :variable problem
In-Reply-To: <20030820180528.GA89815@pcslink.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox