Jan, thanks for test case we will debug and answer with our findings. As of long and Long datatypes.
Schema import utility by default generate primitive types (long, int,...) for NOT NULL fields and classes (Long, Integer,...) for nullable fields. Type could be changed in UI by clicking on cell with type and select appropriate type for your case. Also could you try our GridGain web console? This utility also could import database metadata and generate POJO + configuration files. See https://ignite.apache.org/addons.html for more details. On Thu, Mar 31, 2016 at 1:10 PM, jan.swaelens <[email protected]> wrote: > In addition to the above, I also find it strange that it generates both > long > and Long types for what seem to be very similar fields, for example: > > /** Value for predecessortypeEnumid. */ > private long predecessortypeEnumid; > > /** Value for successortypeEnumid. */ > private long successortypeEnumid; > > /** Value for durationunitEnumid. */ > private Long durationunitEnumid; > > This might be the cause of another problem I am facing - I'll get back with > more details on it later, just wanted to indicate this as well in case it > might be relevant to the other two observations. > > best regards > jan > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Ignite-Schema-Import-Utility-Mismatch-when-loading-data-between-Date-and-Timestamp-tp3790p3807.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Alexey Kuznetsov GridGain Systems www.gridgain.com
