StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7317706
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-09-06T09:28:12.930
FavoriteCount
0
LastActivityDate
2011-09-06T18:20:10.077
LastEditDate
2011-09-06T18:20:10.077
LastEditorUserId
50476
OwnerUserId
50476
ParentId
7316372
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
You could do the checking of valid super-parks (<code>extends ...</code>) inside the parser grammar, but a tree grammar is less cluttered version of your (combined) grammar: so I like to do such stuff in there. What you could do is create a <code>Set<String> parks</code> as a member of your tree walker: <pre><code>tree grammar CarParkWalker; options { tokenVocab=CarPark; // assuming your combined grammar is called CarPark.g ASTLabelType=CommonTree; } @members { private Set<String> parks = new HashSet<String>(); } // rules here </code></pre> and then add <code>String</code>s to it while the AST is traversed. Then when you stumble upon an <code>extends VALUE</code>, you add some custom code where you check if <code>VALUE.text</code> is present in your <code>Set<String> parks</code>. If not, throw an exception. About mandatory an optional attributes of cars (or car-parks), simply accept zero or more parameters in your (combined) grammar and let your tree grammar rules return a <code>Vehicle</code> instance: <pre><code>/* tree grammar rules! */ vehicle returns [Vehicle v] : car {$v = $car.v;} | motorcycle {$v = $motorcycle.v;} ; car returns [Vehicle v] @init{$v = new Car();} : ^(Car ... ) ; motorcycle returns [Vehicle v] @init{$v = new Motorcycle();} : ^(Motorcycle ... ) ; </code></pre> where a <code>Vehicle</code> may look like: <pre><code>abstract class Vehicle { protected String make; protected String color; protected int age; protected int wheels; // ... } </code></pre> And then check if for each vehicle if all mandatory attributes have been set. If, after trying yourself, you're having trouble implementing all this, I'm willing to post a little demo of it. Just add a comment in that case. Good luck!
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POANTLR - check semantics/meaning of the values
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USBart Kiers
UserOwnerUserId
1. USBart Kiers
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POANTLR - check semantics/meaning of the values
 singulars
 PostTypePostTypeId
 PTQuestion
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTAcceptedByOriginator
CommentsPostId
1. This table or related slice is empty.

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.