Editing Relational state transfer

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 5: Line 5:
"Like REST's requirement to keep state accessible to all possible participating entities in a session, relational databases require that transactions be permanent, and that once committed, the changes stick."
"Like REST's requirement to keep state accessible to all possible participating entities in a session, relational databases require that transactions be permanent, and that once committed, the changes stick."


"The main differences would appear to be the complexity of the arbitrary [[semi-structured data]] that is assumed to be manipulated by [[REST]], the availability of redundant sources (unlike an RDB which explicitly requires each item to be authoritatively in one place in one table), and the necessity of arbitrarily-complex resolution of which data to trust, which is assumed to be a human problem in REST but in relational databases, is more or less assumed to be up to the programs."
etc.
Please note that all contributions to Consumerium development wiki are considered to be released under the GNU Free Documentation License 1.3 or later (see Consumerium:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:

Cancel Editing help (opens in new window)