Hi! Are you talking about Schema Import Utility?
If yes, then it is expected behaviour. Schema Import Utility generates POJOs using java naming convention. To overcome this you may use query fields aliases. But Schema Import Utility with this option (checkbox on UI) will be available in upcoming 1.6 release, or you could use latest nightly build from master. You could use only Schema Import Utility from nightly build and you app may remain on version you are using. About your second problem - could you provide a name of your RDBMs and table script? We will try to reproduce and fix. Hope this help. On Sat, May 7, 2016 at 10:25 PM, minisoft_rm <[email protected]> wrote: > dear experts, I meet troubles that very boring : > trouble 1: > I noticed that ignite generates fields without underscore... i.e. remove it > if my table column : > p_baseprice -> pBaseprice > > trouble2: > ignite treats int(1) as Boolean.... how to indicate it as just integer??? > > > please confirm if ignite is doing the above things.... and how to change > them? I actually modified pBaseprice back to p_baseprice manually.(so > boring...) > > but, after I change Boolean to integer. the starting ignite server process > throws exception. > > I am in mess at all. please clarify if manual changes(from Boolean to > Integer) work? i am modifying the "ServerConfigurationFactory.java" of > course. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/trouble-about-Underscore-and-Boolean-tp4840.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
