StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19850557
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
2
CommunityOwnedDate
CreationDate
2013-11-08T02:29:07.577
FavoriteCount
0
LastActivityDate
2013-11-08T02:34:24.087
LastEditDate
2013-11-08T02:34:24.087
LastEditorUserId
186909
OwnerUserId
186909
ParentId
19850287
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
The username field you pass to init is basically the file name for the store, for example: <code>WL.JSONStore.init(..., {username: 'store1'})</code> You will have store1.sqlite on disk, no encryption. If you want to switch to another store simply call: <code>WL.JSONStore.closeAll()</code> The closeAll function will kill all database accessors. Then you can start a second store with a password, for example: <code>WL.JSONStore.init(..., {username: 'store2', password: '123'})</code> That will create a store2.sqlite file encrypted with 256-bit AES encryption. If you want to switch back to store1, simply call <code>WL.JSONStore.closeAll()</code> and then <code>WL.JSONStore.init(..., {username: 'store1'})</code>. Currently you can not access store1 and store2 at the same time. You can open a feature request <a href="https://www.ibm.com/developerworks/community/forums/html/topic?id=77777777-0000-0000-0000-000014907906&ps=25" rel="nofollow">here</a>. The .sqlite files are mentioned <a href="http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/index.jsp?topic=%2Fcom.ibm.worklight.help.doc%2Fdevref%2Fc_jsonstore_support.html" rel="nofollow">here</a> if you want to see them on the file system, and a bit of their internal structure is mentioned <a href="http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/topic/com.ibm.worklight.help.doc/devref/r_jsonstore_store_internals.html" rel="nofollow">here</a>. The code snippets above don't show it, but make sure you take into account that most JSONStore API functions are async, read more <a href="http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/topic/com.ibm.worklight.help.doc/devref/r_jsonstore_asynch_callbacks_promises.html" rel="nofollow">here</a>.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWorklight v6: use multiple JSON stores concurrently in app
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. UScnandreu
UserOwnerUserId
1. UScnandreu
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POWorklight v6: use multiple JSON stores concurrently in app
 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. COThanks for the detailed answer. I think this kind of information should be in the official documentation, and there needs to be more examples.
 singulars
 PostPostId
 PO
 UserUserId
 USuser2956676
2. CO@user2956676 It would be helpful if you explain what confused you or what you didn't understand from reading the official documentation. Did you read it all? There's [general docs](http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/topic/com.ibm.worklight.help.doc/devref/c_jsonstore_overview.html), [API docs](http://pic.dhe.ibm.com/infocenter/wrklight/v6r0m0/topic/com.ibm.worklight.help.doc/devref/c_wl_jsonstore_core_api.html) and [example code](http://www.ibm.com/developerworks/mobile/worklight/getting-started.html#advanced-client-side-development). Feedback is appreciated.
 singulars
 PostPostId
 PO
 UserUserId
 UScnandreu

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.