Path: newssvr20.news.prodigy.com!newsmst01.news.prodigy.com!prodigy.com!rip!sjc70.webusenet.com!news.webusenet.com!sn-xit-02!sn-xit-01!sn-post-01!supernews.com!corp.supernews.com!not-for-mail From: Daniel Morgan Newsgroups: comp.databases.oracle.server Subject: Re: Caching within packages.. Date: Fri, 12 Dec 2003 16:37:53 -0800 Organization: ATS Message-ID: <1071275778.879126@yasure> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en MIME-Version: 1.0 References: <3fd64fd1.3892236@nyc.news.speakeasy.net> <3amctv8cv1lkj0ag7eeqlkm10a3rmg7c8t@4ax.com> <3fd74f4e.69297113@nyc.news.speakeasy.net> <1071076405.507455@yasure> <3fd78e4d.85423352@nyc.news.speakeasy.net> <1071107232.781138@yasure> <3fd89b34.154262547@nyc.news.speakeasy.net> <1071178457.618853@yasure> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cache-Post-Path: yasure!unknown@oracle.advtechserv.com X-Cache: nntpcache 2.4.0b5 (see http://www.nntpcache.org/) X-Complaints-To: abuse@supernews.com Lines: 44 Xref: newssvr20.news.prodigy.com comp.databases.oracle.server:250031 Joachim Zobel wrote: > On Thu, 11 Dec 2003 13:35:52 -0800, Daniel Morgan wrote: > > >>NetComrade wrote: >> >> >>>On Wed, 10 Dec 2003 17:48:48 -0800, Daniel Morgan >>> wrote: >>> >>> >>> >>>>So every time someone makes a change to a table you are going to bounce >>>>the server? Do you really advocate that? If so I'd suggest you keep >>>>really quiet during job interviews. >>> >>> >>>Not necessarily 'bounce', more like a refresh (reconnect). Out app >>>server is capable of that.. >> >>Apparently you do not understand the concept that was described in the >>previous posts. What you propose will not work. > > > The cached table is package state, which lives on a per session basis. So > a reconnect will reload the cached table. What exactly do you mean by > "will not work"? > > Sincerely, > Joachim Make a change to a table in one session and the in-memory table becomes invalid in every other session and you have no means of refreshing it other than bouncing every single user off the system every time that happens. I define that as "will not work". -- Daniel Morgan http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp damorgan@x.washington.edu (replace 'x' with a 'u' to reply)