Calvin,
it doesn't.
When you look at the SQL statements that are sent to the other side (by running DBREMOTE -v -o C:\´MyLog.txt) you will notice that the receiving database gets a complete statement with the *last_update* column set. And the particular DEFAULT TIMESTAMP default will only be applied when the column's value is not set explicetely.
So no need to worry, we have used this DEFAULT in a SQL Remote setup for years.
As to your new example: If the remote exeucutes the following SQL statement (say, in a client app):
UPDATE people SET last_name = 'Smith' WHERE id = 123450000
then last_update will be set automatically to current timestamp (say, to '2010-01-28 11:24:23.123456'). The transaction log will then contain something like (you could check by using DBTRAN):
UPDATE people SET last_name = 'Smith', last_update = '2010-01-28 11:24:23.123456' WHERE id = 123450000
And it's that statement that is sent to the consolidated. Obviously, the statement contains a value for the DEFAULT TIMESTAMP column, so it doesn't update *last_update* again.
answered
27 Jan '10, 18:45
Volker Barth
39.8k●358●546●815
accept rate:
34%
Your example is somewhat lacking a "real" column: You wouldn't want to update the id (as a PK field) in a SQL Remote setup, otherwise last_update wouldn't be the problem:)
Example updated.