1. I have a server with a database and I would like to have two
clients.
2. Then make i a view from one table. I use this view in both clients.
3. Client 1 modifiy the view

I would like that client 2 can fast this change receive.

Thank you

Moi wrote:
For that to happen, first client 1 must commit the changes, then client
2 must restart the query. Oracle uses a read consistancy model so you
never see dirty (uncommitted) data. This is well documented in the
manuals. Please read them.

Also Oracle questions will often receive better, faster answers in the
appropriate Oracle group, including:

comp.databases.oracle.server
Group description: Oracle database administration/server topics.
configuration, maintenance and similar topics

comp.databases.oracle.tools
Group description: Oracle software tools/applications.
such as Oracle Forms, SQLPLUS.

comp.databases.oracle.marketplace
Group description: Oracle-related jobs, etc.
including product announcements

comp.databases.oracle.misc
Group description: Oracle related topics.
not covered by the other groups. (IOW don't post ads here, use
marketplace!)


Ed

Moi wrote:
Another question is what has your posting to do with the subject?
"Distributed database" typically refers to environments where there is
more than one /server/ instance.

robert

Robert Klemme wrote:
Either way it's not only a FAQ but an important one - how to any two accessors
of the same data, server or client, remain in "synchrony" (a.k.a., "fast this
change receive").

Part of the answer lies in deep analysis of "synchrony" and "fast", which
translate into questions of latency and simultaneity.

Point 1: Simultaneity is relativistic: it depends on your frame of reference.
Put another way, there is no simultaneity, only epsilon so that your
measured information latency is less than epsilon.

Point 2: Information latency is resolvable if at all then by accounting for
information value, which is sociological, and expressing value as a function
of entropy, i.e., the older your information, the less valuable.

Point 3: Information value exceeds required value for some time then it is too
old. Determination of that minimum required value helps determine tolerable
latency.

The overall problem is cognate for replication and for multiple clients.

- Lew

"Moi" <mromerooca (AT) gmail (DOT) com> wrote:



Look at events in Interbase/Firebird. You can signal an event to a
client through a Delphi app, however, I don't believe that you can do
this through any web-enabled client, unless you can force a refresh
every so often.


Paul...


--

plinehan __at__ yahoo __dot__ __com__

XP Pro, SP 2,

Oracle, 9.2.0.1.0 (Enterprise Ed.)
Interbase 6.0.1.0;

When asking database related questions, please give other posters
some clues, like operating system, version of db being used and DDL.
The exact text and/or number of error messages is useful (!= "it didn't work!").
Thanks.

Furthermore, as a courtesy to those who spend
time analysing and attempting to help, please
do not top post.