<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Client Server Database by Kierit LEHAL</title>
      <link>https://padlet.com/klehal1/ihrh13u6zjpcvem9</link>
      <description></description>
      <language>en-us</language>
      <pubDate>2023-09-28 08:35:40 UTC</pubDate>
      <lastBuildDate>2023-09-28 09:11:19 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Advantages</title>
         <author>klehal1</author>
         <link>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724306405</link>
         <description><![CDATA[<div>The consistency of the database is maintained because only one copy of data is held rather than 1 at each workstation<br><br>Expensive - powerful computer/server - available for many users <br><br>Access rights and security can be managed centrally<br><br>backup and recover can also be managed centrally</div>]]></description>
         <enclosure url="" />
         <pubDate>2023-09-28 08:38:41 UTC</pubDate>
         <guid>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724306405</guid>
      </item>
      <item>
         <title>How it Works</title>
         <author>klehal1</author>
         <link>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724311066</link>
         <description><![CDATA[<div>Records are copied locally to machine allowing user to edit on client side<br>Edited copy is then send back to central server</div>]]></description>
         <enclosure url="" />
         <pubDate>2023-09-28 08:42:34 UTC</pubDate>
         <guid>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724311066</guid>
      </item>
      <item>
         <title>Record Locks</title>
         <author>klehal1</author>
         <link>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724319973</link>
         <description><![CDATA[<div>A record is locked when a client retrieves the data from it - this locks anyone else out from attempting to retrieve it<br><br>This solves the issue of multiple people changing one record at once<br><br>ISSUE<br>If two users are changing two separate records that are linked neither user could change the record and a DEADLOCK is reached.<br><br>Solved by serialisation <br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2023-09-28 08:49:26 UTC</pubDate>
         <guid>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724319973</guid>
      </item>
      <item>
         <title>Serialization </title>
         <author>klehal1</author>
         <link>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724322886</link>
         <description><![CDATA[<div>This is a technique which ensure that transactions do not overlap in time - cannot interfere with each other or lead to updates being lost. A transaction cannot start until the previous one has finished&nbsp;<br><br>implemented using time stamp ordering or commitment ordering</div>]]></description>
         <enclosure url="" />
         <pubDate>2023-09-28 08:51:28 UTC</pubDate>
         <guid>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724322886</guid>
      </item>
      <item>
         <title>Timestamp ordering</title>
         <author>klehal1</author>
         <link>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724325635</link>
         <description><![CDATA[<div>When a transaction starts it is given a timestamp - so if 2 transactions affect the same object - the transaction with the earliest one will be applied first<br><br>In order to ensure transactions aren't lost - each object has a read timestamp and a write timestamp - both updated when an object is read or written</div>]]></description>
         <enclosure url="" />
         <pubDate>2023-09-28 08:53:54 UTC</pubDate>
         <guid>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724325635</guid>
      </item>
      <item>
         <title>Commitment Ordering</title>
         <author>klehal1</author>
         <link>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724328707</link>
         <description><![CDATA[<div>This is another serialization technique&nbsp;<br><br>Transactions are ordered in terms of their dependencies on each other as well as the time they were initiated&nbsp;<br><br>It can avoid a deadlock by blocking one request until another is completed</div>]]></description>
         <enclosure url="" />
         <pubDate>2023-09-28 08:56:41 UTC</pubDate>
         <guid>https://padlet.com/klehal1/ihrh13u6zjpcvem9/wish/2724328707</guid>
      </item>
   </channel>
</rss>
