StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3630941
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-09-02T20:25:04.780
FavoriteCount
0
LastActivityDate
2010-09-05T23:51:27.833
LastEditDate
2010-09-05T23:51:27.833
LastEditorUserId
71589
OwnerUserId
71589
ParentId
3630641
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The web2py Database Abstraction layer does not support SOLR at this time which means you cannot use the DAL syntax for accessing SOLR and you cannot use automatically generated forms from a SOLR DB schema. Yet you can generate forms using SQLFORM.factory as-if you had a normal relational database and perform the insert/update/select/update into SOLR manually. web2py includes libraries for parsing/writing both JSON and XMl so it will be easy to implement SOLR APIs in few lines of code. If you bring this up on the web2py mailing list we can help with some examples. EDIT (copied from the answer on the web2py mailing list): Normally in web2py you define a model <pre><code>db.define_table('message',Field('body')) </code></pre> and then web2py generates and processes forms for you: <pre><code>form=SQLFORM(db.message) if form.accepts(request.vars): do_something </code></pre> In your case you would not use define_table because web2py DAL does not support SOLR and you cannot generate forms from the schema but you can install this: <a href="http://code.google.com/p/solrpy/" rel="nofollow noreferrer">http://code.google.com/p/solrpy/</a> and you can do <pre><code>#in model import solr s = solr.SolrConnection('http://example.org:8083/solr') #in controller form=SQLFORM.factory(Field('body')) if form.accepts(request.vars): s.add(mody=request.vars.body) s.commit() do_something </code></pre> So the difference is SQLFORM.factory instead of SQLFORM and the extra line after accepts. That is it. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhat's the most productive frontend framework to use with SOLR as the backend?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USmdipierro
UserOwnerUserId
1. USmdipierro
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. COGreat - will do that /me is amazed how quickly mdipierro responds to a web2py related question ;)
 singulars
 PostPostId
 PO
 UserUserId
 USHarryF

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.