StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3247525
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-07-14T15:06:50.570
FavoriteCount
0
LastActivityDate
2010-07-14T15:45:19.593
LastEditDate
2010-07-14T15:45:19.593
LastEditorUserId
370585
OwnerUserId
370585
ParentId
3247369
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
It is hard to tell what you are asking, but according to the <a href="http://java.sun.com/docs/books/jls/second_edition/html/classes.doc.html#228080" rel="nofollow noreferrer">Java Language Specification</a>: In a situation such as this: <pre><code>interface Fish { int getNumberOfScales(); } interface StringBass { double getNumberOfScales(); } class Bass implements Fish, StringBass { // This declaration cannot be correct, no matter what type is used. public ??? getNumberOfScales() { return 91; } } </code></pre> It is impossible to declare a method named getNumberOfScales with the same signature and return type as those of both the methods declared in interface Fish and in interface StringBass, because a class can have only one method with a given signature (§8.4). Therefore, it is impossible for a single class to implement both interface Fish and interface StringBass. However, if both of your interfaces specify the same return type, then you can go ahead and implement that method. If <code>MyUser</code> and <code>YourUser</code> have a common ancestor then you could do <code>List<? extends User></code> or if they have no commonality you can use simply use <code>List<?>.</code> At that point though, you have to stop and consider if a common implementation is what you actually want. I suspect there may be a more elegant solution, if you provided us with more details about your problem. Edit: Based on your comment, you want something like... <pre><code>interface MyUserGetter { List<? extends MyUser> getUsers(); } interface YourUserGetter { List<? extends YourUser> getUsers(); } class UserGetterImpl { List<? extends UserImpl> getUsers(); } </code></pre> This is untested, and I'd guess has a 50% chance of working. The architectural suggestion is that instead of having a single implementation for two interfaces you might actually want two implementations of one interface: <pre><code>interface User {} class MyUser implements User {} class YourUser implements User {} interface UserGetter { List<? extends User> getUsers(); } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POproblem with wildcards and one class which implements two interfaces
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMikeD
UserOwnerUserId
1. USMikeD
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. 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
 VTUpMod
CommentsPostId
1. COYes, but you can do this: interface MyUser{} interface YourUser{} class UserImpl implements MyUser, YourUser {} interface MyUserGetter{ MyUser getUser();} interface YourUserGetter{ YourUser getUser();} class UserGetterImpl implements MyUserGetter, YourUserGetter { public UserImpl getUser() { return new UserImpl(); } } I want to add methods List<MyUser> getUsers() inside MyUserGetter interface, and List<YourUser> getUsers() inside YourUserGetter interface, and the only one implementation List<?????> getUsers() inside UserGetterImpl
 singulars
 PostPostId
 PO
 UserUserId
 USGeorgi Georgiev

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.