> The statement is the client controlled operation that causes

everything else to happen.

A-ha! That explains it. The way it was originally stated it sounded
like the statement that actually made the change, in which case it would
only make sense for an insert or update that took a long time to run.

This is also what I was fishing for when I asked about a transaction
timestamp. What I really meant was a client-initiated-action timestamp.

> if your whole application is a series of linked stored procedures

Yes, this portion is. No business logic needed, just a lot of inventory
accounting that in the end results in a bunch of purchase orders.

-----Original Message-----
From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Ann W. Harrison
Sent: Wednesday, January 31, 2007 1:05 PM
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] CURRENT_TIMESTAMP vs. NOW

Rick Debay wrote:

>> How big is the external table?
>
> 632 bytes.

Well, that's not a factor.

The statement is the client controlled operation that causes everything
else to happen. So, if your whole application is a series of linked
stored procedures and triggers, the whole application is a single
statement.


Regards,


Ann

Disclaimer: This message (including attachments) is confidential and may be privileged. If you have received it by mistake please notify the sender by return e-mail and delete this message from your system. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. Please note that e-mails are susceptible to change. RxStrategies, Inc. shall not be liable for the improper or incomplete transmission of the information contained in this communication or for any delay in its receipt or damage to your system. RxStrategies, Inc. does not guarantee that the integrity of this communication has been maintained nor that this communication is free from viruses, interceptions or interference.