pg.ddx.io pgsql-interfaces@postgresql.org mailing list archivehelp / color / mirror / Atom feed
ECPG - cursor fetch 2+ messages / 2 participants [nested] [flat]
* ECPG - cursor fetch @ 2005-03-10 21:51 Mark Richardson <markmapo@yahoo.com> 2005-03-13 10:57 ` Re: ECPG - cursor fetch Michael Meskes <meskes@postgresql.org> 0 siblings, 1 reply; 2+ messages in thread From: Mark Richardson @ 2005-03-10 21:51 UTC (permalink / raw) To: pgsql-interfaces I'm doing a port from Sybase's pre-compiler cpre, to ecpg and I have a couple of questions (if anyone has the time). This relates to cursors and fetching, and what I would like to do is retrieve a bunch of records at one time - cpre is able to fetch values into an array... EXEC SQL BEGIN DECLARE SECTION; int myInts[100]; EXEC SQL END DECLARE SECTION; ... EXEC SQL DECLARE myCursor FOR SELECT myInt FROM myTable; EXEC SQL FETCH myCursor INTO :myInts; There is one mechanism that cpre uses to make sure that you don't exceed the array size... EXEC SQL OPEN myCursor ROW_COUNT=100; then, every time you do a fetch, it retrives 100 rows. I'm not asking for this exact thing in ecpg, but what mechanisms are available for a similar type of response, rather than looping the fetch statement a bunch of times? Also, since I'm in the middle of a port, I'm trying to make the code work for both with a different compile flag - but the pre-compilers don't care about #defines. Is there some other mecanism to tell ecpg to ignore or skip a section? I really don't want to have to make a "Pre-pre-compiler". I thought I would share this - the ecpg pre-compiler is much easier to work with, and it handles things better than cpre when it comes to code generation. I think it would be much easier to port from ecpg to cpre than what I am doing, because a lot of the non-standard options that are available used/forced in cpre. So thanks for all the work you guys have done. --------------------------------- Do you Yahoo!? Yahoo! Small Business - Try our new resources site! ^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: ECPG - cursor fetch 2005-03-10 21:51 ECPG - cursor fetch Mark Richardson <markmapo@yahoo.com> @ 2005-03-13 10:57 ` Michael Meskes <meskes@postgresql.org> 0 siblings, 0 replies; 2+ messages in thread From: Michael Meskes @ 2005-03-13 10:57 UTC (permalink / raw) To: Mark Richardson <markmapo@yahoo.com>; +Cc: pgsql-interfaces On Thu, Mar 10, 2005 at 01:51:07PM -0800, Mark Richardson wrote: > I'm doing a port from Sybase's pre-compiler cpre, to ecpg and I have a couple of questions (if anyone has the time). This relates to cursors and fetching, and what I would like to do is retrieve a bunch of records at one time - cpre is able to fetch values into an array... > EXEC SQL BEGIN DECLARE SECTION; > int myInts[100]; > EXEC SQL END DECLARE SECTION; > ... > EXEC SQL DECLARE myCursor FOR SELECT > myInt FROM myTable; > > EXEC SQL FETCH myCursor INTO > :myInts; > > There is one mechanism that cpre uses to make sure that you don't exceed the array size... > EXEC SQL OPEN myCursor ROW_COUNT=100; > then, every time you do a fetch, it retrives 100 rows. This is usually done in the fetch statement and not in the open one. Just use EXEC SQL FETCH 100 myCursor INTO :myInts; > Also, since I'm in the middle of a port, I'm trying to make the code work for both with a different compile flag - but the pre-compilers don't care about #defines. Is there some other mecanism to tell ecpg to ignore or skip a section? I really don't want to have to make a "Pre-pre-compiler". EXEC SQL DEFINE/IFDEF/... > I thought I would share this - the ecpg pre-compiler is much easier to work with, and it handles things better than cpre when it comes to code generation. I think it would be much easier to port from ecpg to cpre than what I am doing, because a lot of the non-standard options that are available used/forced in cpre. So thanks for all the work you guys have done. Nice to hear that. :-) Michael -- Michael Meskes Email: Michael at Fam-Meskes dot De ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL! ^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2005-03-13 10:57 UTC | newest] Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2005-03-10 21:51 ECPG - cursor fetch Mark Richardson <markmapo@yahoo.com> 2005-03-13 10:57 ` Michael Meskes <meskes@postgresql.org>
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