Not sure how something can be writable in read only mode. Seems like a
contradition. v$session already tracks each user, you could do that. Read
up on application context.
Jim
--
Replace part of the email address: kennedy-down_with_spammers_at_attbi.com
with family. Remove the negative part, keep the minus sign. You can figure
it out.
"Konstantin Kudin" <konstantin_kudin_at_yahoo.com> wrote in message
news:ff88eb34.0307091218.373b70a3_at_posting.google.com...
> Hi,
>
> I am curious if it is possible to create a temporary table (in Oracle
> 8.1.7) that would be visible to all sessions. Then its data would go
> away when the database is shutdown. Hopefully, due to its temporary
> nature such a table would also be writable in read-only mode.
>
> A possible usage would be to keep track of web users when each user
> is issued an ID on web logon. The ID is passed back and forth as a
> cookie or a hidden form field to authenticate the user. Stored
> procedures would validate legitimacy of requests by the ID. The IDs
> would be stored in an all session visible temporary table.
> Hypothetically if the database is opened in read-only mode, the users
> can still login from the web, get IDs, and do at least some things
> since the table with IDs is hopefully writable. Is this possible or is
> there a better way?
>
> I know that Oracle has "global temporary" tables, which are either
> session-specific or transaction-specific. Are these writable in
> read-only mode? There is a way to make sure that Oracle can sort in
> read-only mode and thus perform writes to a temporary tablespace.
> Would the same mechanism work with "global temporary" tables thus
> making them writable, or not?
>
> Thanks!
>
> Konstantin
Received on Wed Jul 09 2003 - 19:55:47 CDT
