|Re: [eclipselink-users] Undetected problem mapping fields to columns|
I still don't see the attachement. It is probably best to do this in bugzilla: https://bugs.eclipse.org/bugs/File a bug for the project: RT (RuntimeProject) and EclipseLink. You can add attachments to your bug.
-Tom Rui Jesus wrote:
I suppose you prefer a single file including all annexes! Here you are! Thanks. tware wrote:I don't see the attachements, but please file a bug including your problem description and attachments.Rui Jesus wrote:I forgot the attachments... Rui Jesus wrote:http://old.nabble.com/file/p30194812/AnotherConcreteEvent.java AnotherConcreteEvent.java http://old.nabble.com/file/p30194812/console-output.txt console-output.txt http://old.nabble.com/file/p30194812/EventsDAO.java EventsDAO.java http://old.nabble.com/file/p30194812/EventsDAOImpl.java EventsDAOImpl.java http://old.nabble.com/file/p30194812/EventsTest.java EventsTest.java http://old.nabble.com/file/p30194812/OneConcreteEvent.java OneConcreteEvent.java http://old.nabble.com/file/p30194812/persistence.xml persistence.xml http://old.nabble.com/file/p30194812/EventsTest-context.xml EventsTest-context.xmlJPA provider seems to be unable to detect a potential problem when mapping fields to columns. Having an hierarchy of entities using a single-table strategy, and two entities having fields with same name but different types, results that in a future persist action, a "java.sql.SQLDataException: data exception: invalid character value for cast" is thrown. This is because no two columns exist for the two different fields. I am using version "eclipselink-2.1.1.v20100817-r8050", Springframework-3.0.4, and JUnit-4.8.2. This problem one can reproduce! As annexes, I provide several files including java test files, captured console output, etc._______________________________________________ eclipselink-users mailing list eclipselink-users@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/eclipselink-users
Back to the top