|Re: [eclipselink-users] Custom SQL for relationship|
Isn't a stored procedure database/vendor specific? Wouldn't be a contrary approach, because my understanding of JPA is, that it is a Object Relational Mapping technique, so that you can exchange your database. Couldn't be retrieving the default company implemented as extra method getDefaultCompany() be easier? Code the logic in Java. So you still can switch to another database. Hope this will help. Maybe there are performance reasons? -- View this message in context: http://old.nabble.com/Custom-SQL-for-relationship-tp30315811p30318226.html Sent from the EclipseLink - Users mailing list archive at Nabble.com.
Back to the top