Hello, Yes I totally agree that the generated Java class should follow the well known conventions.
An intermediate solution might be (I say might since I do not know the inner workings of Ignite) to have the variables 'ugly' in the Java class and have pretty accessors (get/set). All 'better' solutions will result in a high impact change as far as I can tell by adding an interpreter which reformulates the sql syntax from raw sql to a sql matching the java classes field names - I'm quite sure that's something you won't even want in the product since it increases overhead. br jan -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/SQL-Aliases-are-not-interpreted-correctly-tp4281p4327.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
