From: Michael H. <mic...@el...> - 2005-02-23 09:15:12
|
Milan Babuskov wrote: > Now it does not crash anymore, nor I have any other problems. Except > one: it only fetches first 299 records. To make sure, I did a > count(*) on table, and it has 1000+ records... Yes, sorry, I noticed after I committed yesterday; I had hoped I would be able to correct it before somebody noticed :-( It is fixed now in CVS. Anyway, this whole thing is twofold: 1) I feel that the current code is better, because the event handler is not burning cycles when there is nothing (more) to fetch in the background. That's good. 2) The change was necessary, because with the static IDLE handler tableM->fetch() would be called, which would always throw inside of IBPP::Statement methods after execution of a faulty select statement. I find the API design there kind of unfortunate, it's not even possible to call IBPP::Statement::Columns() without making sure that a result set is available. There would be *no* *harm* in returning 0 instead. I really think exceptions are slightly misused in IBPP. Best -- Michael Hieke |