This is just unbelievable! As I expected using this property has side effects.
We have boolean fields defined in our database as number(1,0) because Oracle does not know boolean type. Now we get ArgumentExceptions saying that we declare columns that are not compatible with the expected type "bit". These errors never showed up before we added the property "openjpa.jdbc.SchemaFactory". Now what? Remove the property and use OneToMany instead of OneToOne relationships with programmatically limit the number of child elements to one only? This would be very awful. Are there any other options we have got? -- View this message in context: http://openjpa.208410.n2.nabble.com/Constraint-violation-using-OneToOne-relationship-tp6978223p6980990.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
