At 02:11 AM 24/01/2006, Andi wrote:

>Hello firebird-support,
>
> I have 2 databases. The 1st database has a table that contains
>timestamp data type. This table doesn't have trigger or something
>else. It's just a table. Every update to this table, the field) that
>type is timestap) always update with the current date and time
>automatically.

If this is happening, then *something* is causing the timestamp to be
updated. If it is not an update trigger, then it is your application
code that is doing it.

If it was writing timestamps automatically on inserts only, and only
when that column was not included in the INSERT statement, then one
could suppose that the column is defined with a DEFAULT clause, e.g.
DEFAULT CURRENT_TIMESTAMP, or under a domain that has that default
defined. But it would not set any value on updates, nor on any
insert statements that included a value for the that column.

> But the 2nd database (which has a table that contains timestamp
>data type too, but different structure) doesn't update the field
>with the current date and time automatically everytime update occurs.

What is meant by "but different structure"? The table structure is
different, or the timestamp column is different?

>What's wrong with this table?

The 64-million dollar question....probably nothing wrong, except that
it's missing a trigger. There's nothing magical about a timestamp
column that makes it automatically write itself.

./heLen