<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Persistent classes - Locking a table before update in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379165#M1403049</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have to create a persistence class for each table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use option 1.  Option 2 couples business meaning into your persistence layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 09 Dec 2009 10:36:03 GMT</pubDate>
    <dc:creator>matt</dc:creator>
    <dc:date>2009-12-09T10:36:03Z</dc:date>
    <item>
      <title>Persistent classes - Locking a table before update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379162#M1403046</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am thinking about using persistent classes for my CRUD application. However I am unclear about 1 thing... do i have to lock the Db tables before calling the SET_ methods or create_persistent methods ? I went to the SAP reference site Link: [http://help.sap.com/saphelp_nw04/helpdata/en/f5/a3682ebc6911d4b2e80050dadfb92b/content.htm] there they say that they have not implemented the Lock concept yet. Seems like persistent classes are missing a really fundamental thing if they do not lock a Db table before update( or am I misinterpreting something ? ). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So do I explicitly call the ENQUEUE n DEQUEUE FMs to lock the Db table before the SET_ methods? parallel access is possible in my app.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 06 Dec 2009 14:58:59 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379162#M1403046</guid>
      <dc:creator>aditya_aghor</dc:creator>
      <dc:date>2009-12-06T14:58:59Z</dc:date>
    </item>
    <item>
      <title>Re: Persistent classes - Locking a table before update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379163#M1403047</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;So do I explicitly call the ENQUEUE n DEQUEUE FMs to lock the Db table before the SET_ methods?&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 06 Dec 2009 23:57:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379163#M1403047</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2009-12-06T23:57:16Z</dc:date>
    </item>
    <item>
      <title>Re: Persistent classes - Locking a table before update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379164#M1403048</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rich,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1 more question .. if i have multiple Db tables related to 1 logical entity (eg Logical entity is customer and it has multiple Ztables to store customer's data) so I would have to create a persistent class for each of the Ztables correct ? then which of the following approaches is the best&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Write a wrapper class to represent the Business entity customer and inside that wrapper class call the locking methods and the GET_  &amp;amp; SET_ methods &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Add the other persistent classes as attributes of the main persistent class( as type ref to so that its corresponding GET_, SET_ methods are auto generated ). eg. IF the are two tables ZCUST, ZCUST_COMP_CODE then we would have 2 persistent classes. Should I add the persisent class of ZCUST_COMP_CODE to ZCUST ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Dec 2009 05:49:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379164#M1403048</guid>
      <dc:creator>aditya_aghor</dc:creator>
      <dc:date>2009-12-09T05:49:03Z</dc:date>
    </item>
    <item>
      <title>Re: Persistent classes - Locking a table before update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379165#M1403049</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You have to create a persistence class for each table. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Use option 1.  Option 2 couples business meaning into your persistence layer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Dec 2009 10:36:03 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379165#M1403049</guid>
      <dc:creator>matt</dc:creator>
      <dc:date>2009-12-09T10:36:03Z</dc:date>
    </item>
    <item>
      <title>Re: Persistent classes - Locking a table before update</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379166#M1403050</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thx guys!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Dec 2009 06:37:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/persistent-classes-locking-a-table-before-update/m-p/6379166#M1403050</guid>
      <dc:creator>aditya_aghor</dc:creator>
      <dc:date>2009-12-10T06:37:38Z</dc:date>
    </item>
  </channel>
</rss>

