Re: ecpg weird behavior
От | Thomas Lockhart |
---|---|
Тема | Re: ecpg weird behavior |
Дата | |
Msg-id | 3C922B46.BA9F85D@fourpalms.org обсуждение исходный текст |
Ответ на | ecpg weird behavior ("Nicolas Bazin" <nbazin@ingenico.com.au>) |
Список | pgsql-interfaces |
... > > EXEC SQL FETCH curs_currency; > Anyone out there with more knowledge about standards? I thought this was > not standard at all. From what I can tell from my SQL99 maybe-docs we have all shared in the past on this list, the INTO is required to travel with the FETCH statement: <dynamic fetch statement> ::= FETCH [ [ <fetch orientation> ] FROM ] <dynamic cursor name> <output using clause> <output using clause> ::= <into arguments> | <into descriptor> <into arguments> ::= INTO <into argument> [ { <comma> <into argument> }... ] <into argument> ::= <target specification> <into descriptor> ::= INTO [ SQL ] DESCRIPTOR <descriptor name> hth - Thomas btw, I was working for the first time with ecpg and was very impressed. A company porting from Oracle ran into very few issues. Their existing code *did* have an Oracle extension to use a cursor to select multiple rows into variables declared as arrays. Have you run into this syntax or thought about what it would take to implement it?
В списке pgsql-interfaces по дате отправления: