StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19756045
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-11-03T17:54:59.127
FavoriteCount
0
LastActivityDate
2013-11-03T17:54:59.127
LastEditDate
LastEditorUserId
0
OwnerUserId
683969
ParentId
19727585
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Firstly I would recommend to either use <code>Tastypie</code> - which is out of the box supported by <code>neo4django</code> - instead of <code>Django Rest Framework</code> - or use <code>Django Rest Framework</code> <code>Serializer</code> instead of the <code>ModelSerializer</code> or (worst choice in my opinion) <code>HyperlinkedModelSerializer</code>. As for the error you get, the problem is that <code>neo4django</code> does not return the record id, therefore you get the error. One solution is to override the <code>restore_object</code> function, like this, to include the ID. <pre><code># User Serializer class UserSerializer(serializers.Serializer): id = serializers.IntegerField() username = serializers.CharField(max_length=30) first_name = serializers.CharField(max_length=30) last_name = serializers.CharField(max_length=30) email = serializers.EmailField() password = serializers.CharField(max_length=128) is_staff = serializers.BooleanField() is_active = serializers.BooleanField() is_superuser = serializers.BooleanField() last_login = serializers.DateTimeField() date_joined = serializers.DateTimeField() def restore_object(self, attrs, instance=None): """ Given a dictionary of deserialized field values, either update an existing model instance, or create a new model instance. """ if instance is not None: instance.id = attrs.get('ID', instance.pk) instance.username = attrs.get('Username', instance.username) instance.first_name = attrs.get('First Name', instance.first_name) instance.last_name = attrs.get('First Name', instance.last_name) instance.email = attrs.get('email', instance.email) instance.password = attrs.get('Password', instance.password) instance.is_staff = attrs.get('Staff', instance.is_staff) instance.is_active = attrs.get('Active', instance.is_active) instance.is_superuser = attrs.get('Superusers', instance.is_superuser) instance.last_login = attrs.get('Last Seen', instance.last_login) instance.date_joined = attrs.get('Joined', instance.date_joined) return instance return User(**attrs) </code></pre> But I still think it's better to use <code>Tastypie</code> with <code>ModelResource</code>. Here's a gist by Matt Luongo (or Lukas Martini ?) <a href="https://gist.github.com/mhluongo/5789513" rel="nofollow">https://gist.github.com/mhluongo/5789513</a> TIP. Where <code>Serializer</code> in <code>Django Rest Framework</code>, is <code>Resource</code> in <code>Tastypie</code> and always make sure you are using the github version of neo4django (<code>pip install -e git+https://github.com/scholrly/neo4django/#egg=neo4django</code>)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POAttributeError 'IdLookup' object has no attribute 'rel'
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnikolasd
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POAttributeError 'IdLookup' object has no attribute 'rel'
 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
 VTAcceptedByOriginator
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COThanks a lot. We switched to Tastypie. It worked immediatly!
 singulars
 PostPostId
 PO
 UserUserId
 USuser2944695

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.