  | | | Subject: RE: Issues with multi-queries | Subject: RE: Issues with multi-queries 2007-11-12 - By Ian Daysh
Back With reference to the manual, what is considered a "sufficiently large result set" for the Query::store object? Presumably it's dependant on the size of the program, and the system resources available.
-- --Original Message-- -- From: Warren Young [mailto:mysqlpp@(protected)] Sent: 10 November 2007 03:11 To: MySQL++ Mailing List Subject: Re: Issues with multi-queries
Paul Martin wrote: > I read through the comments in query.h as well and that restated it.
Actually, that form isn't for human consumption directly. The reference manual is generated from these specially-formatted comments, so it's easier to read it there.
http://tangentsoft.net/mysql++/doc/html/refman/
> next time I'll RTFM a little more closely.
That's always good, but also, follow the examples. If the examples do something, don't just remove it if you're not certain why it's there.
Put another way: I've actively tried to cut the code in the examples down as far as I can to make them as simple as possible. What's left is all essential, in one way or another. No fluff.
> With that in mind, if I am calling query.execute() instead of store() > how do I consume the rest of the results?
You don't, so don't do that. More FM to R:
http://tangentsoft.net/mysql++/doc/html/userman/tutorial.html#id2839723
-- MySQL++ Mailing List For list archives: http://lists.mysql.com/plusplus To unsubscribe: http://lists.mysql.com/plusplus?unsub=i.daysh@(protected)
-- MySQL++ Mailing List For list archives: http://lists.mysql.com/plusplus To unsubscribe: http://lists.mysql.com/plusplus?unsub=mysql@(protected)
|
|
 |