Re: [eclipselink-users] Custom SQL for relationship

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

Re: [eclipselink-users] Custom SQL for relationship

From: cinhtau <cinhtau@xxxxxxxxx>
Date: Sat, 27 Nov 2010 04:48:47 -0800 (PST)
Delivered-to: eclipselink-users@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/eclipselink-users>
List-help: <mailto:eclipselink-users-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/eclipselink-users>, <mailto:eclipselink-users-request@eclipse.org?subject=unsubscribe>

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.

Follow-Ups:
- Re: [eclipselink-users] Custom SQL for relationship
  - From: Bálint Kriván

References:
- [eclipselink-users] Custom SQL for relationship
  - From: Bálint Kriván

Prev by Date: [eclipselink-users] Custom SQL for relationship
Next by Date: Re: [eclipselink-users] Custom SQL for relationship
Previous by thread: [eclipselink-users] Custom SQL for relationship
Next by thread: Re: [eclipselink-users] Custom SQL for relationship
Index(es):
- Date
- Thread

Breadcrumbs