Another thread has mentioned:

>>Each EDB engine instance has the ability to dish out a proper incrementing
>>64-bit timestamp that is loosely based upon the current timestamp
>>(date/time) and any interactions with other EDB systems via replication.
>>It's how EDB orders all insert/update/delete operations across the
>>distributed systems.

These useful "Lamport Timestamps" are not yet available to EDB programmers, but maybe could be.

I wonder whether there is a case to be made for the addition of an "ENGINE" key-word to EDB SQL?

This might surface the above variables, and might surface other features which are currently accessible via the EDBEngine component in Delphi but not directly via the SQL.

Adam,

<< These useful "Lamport Timestamps" are not yet available to EDB
programmers, but maybe could be.

I wonder whether there is a case to be made for the addition of an "ENGINE"
key-word to EDB SQL?

This might surface the above variables, and might surface other features
which are currently accessible via the EDBEngine component in Delphi but not
directly via the SQL. >>

Most of the engine information either isn't useful to an SQL script/routine,
or is already surfaced in another way, such as the QUOTEDSTR() function.  In
general, engine information is normally surfaced via the system information
tables, or via specific functions.

--
Tim Young
Elevate Software
www.elevatesoft.com