Hi, Jan. Schema Import utility and Web Console generate code to follow java conventions.
We could discuss an option "Generate POJO with NAMES as in database". >From one point of view this option will be useful when you are going to execute same query as you can run directly on database. >From other hand - generated POJOs will looks ugly and not as idiomatic java POJO. Any way we could discuss this and create appropriate issue in JIRA. My personal option - generate idiomatic Java code. Thoughts? On Tue, Apr 19, 2016 at 5:36 PM, jan.swaelens <[email protected]> wrote: > Hello, > > Ah I see yes, so in order for me to be able to 'switch' our db layer to use > the cache I would need to customize the generator in order to generate > classes and cache definitions matching with the actual tables names. Does > it > work in a case sensitive manner as well or is it case insensitive on field > names like sql is? > > Or would you find it agreeable that the ignite generator has an option to > generate code which allows this out of the box (even when the generated > fields are not really matching the syntax which you would expect in java > classes - i agree). > > br > jan > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/SQL-Aliases-are-not-interpreted-correctly-tp4281p4323.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
