First of all, there is no requirement for using prepared statements. You could always wrap the Dbo backend around normal sql queries.
Secondly, if you opt for using prepared statements in the Mysql backend for Wt::Dbo, then yes, after reading the documentation for usaging prepared statements in MySQL's C api I start seeing your problem. Without getting information from the application about the maximum acceptable amount of memory to occupy you would have to guess a good value without knowing if it fits the application's needs. So there are two possible routes to take: 1) Do not use prepared statements for the mysql backend. This would mean the implementation is not as straight forward as the pgsql or sqlite backend, but it should be possible after all. Is there any specific reason for choosing prepared statements in MySQL over normal queries? 2) Wt starts providing an interface for the 'mysql special case' in prepared statements. In this case I'd rather not see any changes in the existing method signatures but implementation of a specific "options" interface for dbo, where one can get a) a list of parameters a certain backend accepts, b) a method to set specific parameters and c) a method to get the value of such a specific parameter. What do you think about this? /Thomas 2010/3/23 mobi phil <[email protected]>: > Thomas > >> Regarding the ansi quotes: Witty uses ANSI escaping everywhere (last >> time I looked, at least, I have yet to check today's changes). > that was not criticism, but confirmation of a solution that was > proposed earlier, so this issue for the moment should be forgotten.. > >> Regarding the rest: >> In all fairness, I do not understand your kind of problem. Can you >> bring up some SQL/C++ code where MySQL behaves different from SQLite? > > I can help with: > > 1. providing a summary of what I wrote: the last changes of Wt::Dbo > (in git), do not help to improve the MySql driver, as mysqclient > interface needs size information before the fetch, whereas the changes > in design of Wt::Dbo would provide that information at a later stage > in the use cases. > > 2. asking you to read again my email :) > > > -- > rgrds, > mobi phil > > being mobile, but including technology > http://mobiphil.com > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
