Re: select changes in row values?

there is an ordering - just left out for simplicity
assume another column named 'timestamp' exists - some client is then
asked to put a row in the table (timestamp, value) on a periodical
basis. this timestamp value is continously incrementing and used for
ordering the select

after a while, another client wants to retrieve only changes over time
in those values (there are many other columns which values changes on
each insert - it is thus not the inserting clients fault)

does it make sense now?

/aksel

.

Relevant Pages

  • Re: Concurrency Help
    ... The timestamp column is changed whenever ANY data in the row is ... >> An UPDATE operation with a focused WHERE clause is an atomic operation. ... I want to know if a database, ... >>> 1 would overwrite client 2's changes to the db. ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: WSE 2.0 time fault while authentication.
    ... There are two thing that you can use to avoid the timestamp problems: ... It is usually the time skew between client and server machine. ... Syncing the client and server clocks is an impossibility in my case. ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Re: select changes in row values?
    ... | there is an ordering - just left out for simplicity ... | assume another column named 'timestamp' exists - some client is then ... another client wants to retrieve only changes over time ... Michel Cadot ...
    (comp.databases.oracle.misc)
  • Re: select changes in row values?
    ... | there is an ordering - just left out for simplicity ... | assume another column named 'timestamp' exists - some client is then ... another client wants to retrieve only changes over time ... Michel Cadot ...
    (comp.databases.oracle.misc)
  • Re: problems inserting a utf8 timestamp with DBD::Oracle
    ... Don't think so as I'm not using Oracle 9. ... Well I'm not saying it isn't a bug in Oracle but this one is a real problem I cannot easily workaround as really I need a timestamp and a date. ... Client is Oracle 10.2.0 XE ... If you then comment out the 2nd block of code and uncomment the 3rd block of code it works i.e it appears it does not like having a timestamp and a date in the same insert. ...
    (perl.dbi.users)