Thread

1. ecpg stuff

   Michael Meskes <meskes@topsystem.de> — 1998-02-16T08:53:16Z

   Could anyone please enable ecpg compilation in src/interfaces/Makefile again
   as the CVS source now compiles flawlessly.
   
   Anyway, I currently have a list of 5-6 open bugs in ecpg. So if anyone wants
   to help, step forward. :-)
   
   Joking aside, there is one bug or better missing feature that I need some
   input on. Does anyone know what the standards say to the prepare command? Is
   dynamic SQL a standard?
   
   Michael
   -- 
   Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
   meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
   meskes@debian.org                      | 52146 Wuerselen
   Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
   Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10
   
   

2. Re: [HACKERS] ecpg stuff

   Thomas Lockhart <lockhart@alumni.caltech.edu> — 1998-02-17T15:45:16Z

   > Joking aside, there is one bug or better missing feature that I need some
   > input on. Does anyone know what the standards say to the prepare command? Is
   > dynamic SQL a standard?
   
   Yes it is. I have the Date/Darwen book on the SQL standard, and can look up
   answers in the book if you like...
   
                                                     - Tom
   
   
   

3. Re: [HACKERS] ecpg stuff

   Michael Meskes <meskes@topsystem.de> — 1998-02-18T08:12:47Z

   Thomas G. Lockhart writes:
   > > Joking aside, there is one bug or better missing feature that I need some
   > > input on. Does anyone know what the standards say to the prepare command? Is
   > > dynamic SQL a standard?
   > 
   > Yes it is. I have the Date/Darwen book on the SQL standard, and can look up
   > answers in the book if you like...
   
   Yes, I like that. Could you please also lookup:
   
   - the whenever statement
   - and check resp. tell me whether the cursor behaviour is correct. Currently
   the declare statement is send to the backend via PQexec. The open statement
   is ignored and the fetch is executed as fetch via PQexec. I think the data
   shouldn't be processed before the cursor is opened. But I do not know
   what PostgreSQL does with the declare command.
   
   Michael
   
   -- 
   Dr. Michael Meskes, Project-Manager    | topsystem Systemhaus GmbH
   meskes@topsystem.de                    | Europark A2, Adenauerstr. 20
   meskes@debian.org                      | 52146 Wuerselen
   Go SF49ers! Go Rhein Fire!             | Tel: (+49) 2405/4670-44
   Use Debian GNU/Linux!                  | Fax: (+49) 2405/4670-10
   
   

4. Re: [HACKERS] ecpg stuff

   Vadim Mikheev <vadim@sable.krasnoyarsk.su> — 1998-02-18T08:55:40Z

   Michael Meskes wrote:
   > 
   > - and check resp. tell me whether the cursor behaviour is correct. Currently
   > the declare statement is send to the backend via PQexec. The open statement
   > is ignored and the fetch is executed as fetch via PQexec. I think the data
   > shouldn't be processed before the cursor is opened. But I do not know
   > what PostgreSQL does with the declare command.
   
   DECLARE: parser + optimizer + ExecutorStart (initializes plan nodes:
   checks permissions, opens tables & indices). 
   Is OPEN statement in standard ?
   If yes then we could call ExecutorStart() for the OPEN someday.
   
   Vadim