StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20776106
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-12-25T19:29:17.780
FavoriteCount
0
LastActivityDate
2013-12-26T12:37:53.043
LastEditDate
2013-12-26T12:37:53.043
LastEditorUserId
931428
OwnerUserId
931428
ParentId
20736237
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
Before I start answering your question, let me question you domain model. Base class is generally fine, but I want to talk about Person and Customer. You may have good reasons why you picked up inheritance, but please think of composition. Maybe you could have Person that contains a reference to an enum, that states type of the person. You could start here with that: <a href="http://en.wikipedia.org/wiki/Composition_over_inheritance" rel="nofollow">http://en.wikipedia.org/wiki/Composition_over_inheritance</a> <ol> <li>I think you have a typo there. Call save() method on 'customer' not 'Customer', which is a class</li> <li>When there is a request coming to Grails application, it opens a session and the session is available during that request. There is not this kind of behavior like that in Vaadin. You need to put it into a Service. Yes, you can make generic service to save an object class GenericService { def save(def domain) { domain.save(failOnError:true) }} </li> <li>You can get the session factory like this import org.codehaus.groovy.grails.commons.ApplicationHolder as AH def ctx = AH.application.mainContext def sessionFactory = ctx.sessionFactory or ApplicationContext applicationContext = grailsApplication.mainContext ConfigurableLocalSessionFactoryBean factory = applicationContext.getBean('&sessionFactory')</li> <li>As I wrote, you could create GenericService or a service per domain object. Just to keep in mind that GenericService should only save an object and contain no other logic that would be specific for a domain object.</li> </ol>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBasic problems to use Vaadin 7 + Grails 2.3 (Persistence, domain class design, get Hibernate Session)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USOndrej Kvasnovsky
UserOwnerUserId
1. USOndrej Kvasnovsky
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. COThanks a lot for reply. It's very interesting you said, "Composition over inheritance" I'm going check it better. Congratulations and thanks for vaalinonrails website
 singulars
 PostPostId
 PO
 UserUserId
 USRodrigo Rodrigues

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.