Re: [INTERFACES] ECPG Connect user :variable problem

From: Ryan Mooney <ryan(at)pcslink(dot)com>
To: pgsql-interfaces(at)postgresql(dot)org
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [INTERFACES] ECPG Connect user :variable problem
Date: 2003-08-20 18:05:28
Message-ID: 20030820180528.GA89815@pcslink.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-interfaces


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(at)pcslink(dot)com
> <-=-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-=->
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/docs/faqs/FAQ.html

--
>-=-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-<>-=-=-=-=-=-=-<
Ryan Mooney ryan(at)pcslink(dot)com
<-=-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-><-=-=-=-=-=-=->

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Philipp Reisner 2003-08-20 18:46:03 Re: Deadlock in PostgreSQL 7.3.4
Previous Message pgman 2003-08-20 10:14:27 Re: Details

Browse pgsql-interfaces by date

  From Date Subject
Next Message Peter Moscatt 2003-08-24 01:55:11 Writing code to list Databases ?
Previous Message Ryan Mooney 2003-08-20 00:43:07 Re: [INTERFACES] ECPG Connect user :variable problem