A nice way to model data in redis. Pronounce "box".
Before we can store anything, we need to model our data. All we have to do is show boqs how to create an object:
var boqs = ;var User = boqs;
It's pretty much that easy all the time. Notice how we cast our parameters to the types we want. That's because of the way that redis stores data behind the scenes. This was also a design decision made to force your construct functions to explicitly state the structure of the model.
Of course, we could do something a little more fancy (like hashing the user's password), but just keep in mind that construct functions not only used for storing the data, they are also used when the data is pulled out.:
var User = boqs;
While this methodology works, and may be useful, it is not the prettiest solution in my opinion. I recommend keeping your construct functions simple, putting the more intense logic in other parts of your model, and then just calling it when you go to save the object.
To create some new data, we just pass an object to our construct function and save it like so:
var user =username: 'person'password: 'pass'age: 20;user;
To find an object by id:
To get all objects in a collection:
A very simple update function:
A simple delete call:
The MIT License (MIT)Copyright (c) 2015 Paul DilyardPermission is hereby granted, free of charge, to any person obtaining a copyof this software and associated documentation files (the "Software"), to dealin the Software without restriction, including without limitation the rightsto use, copy, modify, merge, publish, distribute, sublicense, and/or sellcopies of the Software, and to permit persons to whom the Software isfurnished to do so, subject to the following conditions:The above copyright notice and this permission notice shall be included in allcopies or substantial portions of the Software.THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS ORIMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THEAUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHERLIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THESOFTWARE.