Well I can't use typed queries because I use JPA 1.0. This is the result of your suggestion:
[7/14/11 16:08:37:205 CEST] 00000013 Query 3 openjpa.Query: Trace: Executing query: SELECT b.id, b.bezeichnung FROM Bp b [7/14/11 16:08:37:205 CEST] 00000013 jdbc_SQL 3 openjpa.jdbc.SQL: Trace: <t 1528126229, conn 690825517> executing prepstmnt 819474648 SELECT t0.ID, t0.BEZEICHNUNG FROM BP t0 [7/14/11 16:08:37:221 CEST] 00000013 jdbc_SQL 3 openjpa.jdbc.SQL: Trace: <t 1528126229, conn 690825517> [16 ms] spent [7/14/11 16:08:51:784 CEST] 00000013 jdbc_JDBC 3 openjpa.jdbc.JDBC: Trace: <t 1528126229, conn 690825517> [0 ms] close 14 seconds. Better. But still far away from fast for reading two little fields... Maybe JPA isn't made for reading tables with many rows. I wonder what developers and users do in the meantime when they have to read and process let's say 800000 or more data rows. Meet the girlfriend in the park? Go on holidays? Hey we are living in the 21st century. Machines have power. ;-) I will try a plain old JDBC database access next and see how it performs. -- View this message in context: http://openjpa.208410.n2.nabble.com/Entity-generation-is-very-time-consuming-tp6579389p6583445.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
