NoSQL.RecentChanges
Edit Page
Page Revisions
|
|
SearchWiki NoSQL.RecentChanges Edit Page Page Revisions |
| Since tables are regular UNIX files, I have so far found no need to implement, and have the associated overhead of, general data access controls in NoSQL. Setting the UNIX permissions on files or directories has proven very useful and effective. This is another example of how the NoSQL system works "with" UNIX, not in addition to it, e.g., not duplicating UNIX functions.
The Revision Control System (RCS) is one of the best configuration management tools available. RCS can be used for version control of many types of files, including tables. Most NoSQL operators can utilize tables that are under RCS control by using a command like:
co -p table | getrow ... | getcolumn ... | prtableThis checks out a table, sends it to 'getrow,' then to 'getcolumn,' and finally prints the data with 'prtable'. In general, any needed series of commands can be constructed to do a given task regardless of whether the tables are checked into RCS. The Concurrent Versioning System (CVS) takes RCS consepts one step further, providing distributed, client-server access to NoSQL tables. A CVS-managed collection of NoSQL tables can be seen as a type of Distributed Relational Database Architecture (DRDA). And one that also provides for disconnected operations! << BigTables | NoSQL.DocumentationIndex | WriteConcurrency >> |