Hi mobi, criticisms are always welcome.
Regarding the ansi quotes: Witty uses ANSI escaping everywhere (last time I looked, at least, I have yet to check today's changes). 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? /Thomas 2010/3/23 mobi phil <[email protected]>: > critics... I hope you do not mind :) > > 1. SET sql_mode='ANSI_QUOTES'; seems to solve the problem, so I will > see if all Wt::Dbo generated instructions are accepted. > thanks for adding the sizes... but .. hm ... it is not exactly what > myqsl (and me :) wants. Sorry if I was not enough clear... > > You added the size to all getResult methods. But when you call on > bind, it is too late! I need (well better say mysql needs) to know the > sizes much before you call bind. Mysql fetches a full row, contrary to > sqlite that fetches only one field. In order to fetch a row, it needs > to know the sizes. So the best is that the constructor of SqlStatement > receives an array with the sizes. Besides that it is useless to have > each time different sizes for each bindResult. The main issue is to > know how much buffer to allocate to make sure that the expected field > size will fit. This is fixed once forever once the C++ Dbo types are > defined. > besides that however with a fast look at git changes, the "create > table" issue is still there. (probably I did not mention it clearly). > Why? The idea was that Wt::Dbo asks the driver's opinion on some > static function about types that should be used for different C++ > types and sizes. Probably would be only the case for string. That is, > if the user defines a std::string size 200 for a C++ field, then mysq > whould suggest a char, instead of TEXT. > > > > -- > 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
