Can you have this fixed in your next release. Issue is that the datatype should be matched. If it is bigint in source it should be long in orientdb, integer should be integer, varchar/string should be string and so on...right now it is buggy also, the column names in source should come up as property names in orientdb...
On Tue, Aug 18, 2015 at 4:13 PM, Giulia Brignoli <[email protected]> wrote: > the only way I know to convert a schema from schema-less to schema-full is > to add the properties in the class from Visual Studio. > I honestly don't think it's a perfect solution, especially if you have > many properties, but unfortunately I can't think of other solutions. > > Regards, > Giulia > > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "OrientDB" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/orient-database/LHZeDtoYqxQ/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
