StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
16760714
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-05-26T15:26:18.917
FavoriteCount
0
LastActivityDate
2013-05-27T12:15:29.357
LastEditDate
2013-05-27T12:15:29.357
LastEditorUserId
2390083
OwnerUserId
2390083
ParentId
16741261
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Have a look at it from a different perspective: More and more web applications are not using "direct SQL" any longer. This enlarges the "distance" between the web developer and SQL/RDBMS. It creates a gap. There are even libraries which go in the opposite direction: No more HQL, just plain SQL. For example, there is <a href="http://www.playframework.com/documentation/2.1.1/ScalaAnorm" rel="nofollow">ANORM</a>, and this means "Anorm is Not an Object Relational Mapper". The given example looks fine and easy. But the whole story is not just table definitions and insert/update/delete. Later you have to query your data, and you may want to query it as fast as possible using all features of your database (window aggregate functions etc.), and at this point ORM could be tricky. As for your question: I suggest inspecting the current data model and queries carefully. Write some prototypes to see whether/how both ways to access data co-exist (caching issues, integration issues etc.). If you cannot switch completely to an ORM mapper, it might be easier to stick with "plain old SQL", and that's OK. It's not the mapper that matters: At the end of the day it's the SQL commands which arrive at your SQL server. And make sure that you can use the most recent version of JPA. One of the earlier versions did not even feature case insensitive sorting. Generally speaking as the version is often defined by your data center (= you have no choice), check if this version does support all the features you need.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJPA coexistence with legacy native SQL
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBeryllium
UserOwnerUserId
1. USBeryllium
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. COMyBatis is a good middle way between ORM approach and native SQL one if you need to keep full control on SQL execution. It remains a good choice for complex legacy or de-normalized databases.
 singulars
 PostPostId
 PO
 UserUserId
 USGab
2. COThanks for your hint. I've generalized the section regarding the "Non-ORM libraries". It was not meant to be a definite list anyway, just an example that there is an alternative approach to using ORMs.
 singulars
 PostPostId
 PO
 UserUserId
 USBeryllium

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.