With expanding expression like "select B from blog B" to "select B.id, B.version, B.name, ... from Block B". Wt should replace table aliases (like B) with lists of all fields of this table (like B.id, B.version, B.name,...). This is useful while constructing complex queries with SQL joins (I used them for QueryModel). I do not remember what was the reason of errors, maybe it was connected with adding of quotation marks near names of fields. WtDboMysql seems not to be developed, therefore can be not compatible with newer versions of Wt::Dbo
On Thu, Jul 7, 2011 at 21:09, PARVINDER RAJPUT <[email protected]> wrote: > > > On Thu, Jul 7, 2011 at 11:38 PM, Nagaev Boris <[email protected]> wrote: >> >> >I have tried this WtDboMysq several months ago and it had problems >> >with some wt methods. >> > What kind of problem sir > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > witty-interest mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/witty-interest > > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
