Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB SQL » View Thread |
Messages 1 to 4 of 4 total |
feature request |
Mon, Dec 28 2009 3:33 AM | Permanent Link |
"Lucian Radulescu" | Hi Tim,
Please, can we have a CURRENT_TRANSACTIONTIME (defined as TIMESTAMP), which would be set when a transaction is started and NUL or even an error would do fine if used outside a transaction. Actually I am interested in a UTC version of the function and perhaps it would make more sense to have the full familly CURRENT_UTC_xxx for all these variables. regards, Lucian |
Mon, Dec 28 2009 9:49 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Lucian,
<< Please, can we have a CURRENT_TRANSACTIONTIME (defined as TIMESTAMP), which would be set when a transaction is started and NUL or even an error would do fine if used outside a transaction. >> Do you mean as an elapsed time figure ? Or a start time only ? -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Dec 28 2009 10:39 AM | Permanent Link |
"Lucian Radulescu" | Tim Young [Elevate Software] wrote:
> Lucian, > > << Please, can we have a CURRENT_TRANSACTIONTIME (defined as > TIMESTAMP), which would be set when a transaction is started and NUL > or even an error would do fine if used outside a transaction. >> > > Do you mean as an elapsed time figure ? Or a start time only ? Start time is what I need and once again UTC time - I think you missed that (duration has nothing to do with UTC). But than you're right, I am not sure how difficult it is, a DURATION for the whole transaction would be nice. I have quite a lot of code around stuff like that which would be nice to get rid of Not sure when exactly I could "read" it though, if I would read it after a commit, how would I know it was my transaction and nobody else's... regards, Lucian |
Tue, Dec 29 2009 9:31 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Lucian,
<< Start time is what I need and once again UTC time - I think you missed that (duration has nothing to do with UTC). >> Just making sure about what you want. I can't always assume that the request makes sense. << But than you're right, I am not sure how difficult it is, a DURATION for the whole transaction would be nice. I have quite a lot of code around stuff like that which would be nice to get rid of Not sure when exactly I could "read" it though, if I would read it after a commit, how would I know it was my transaction and nobody else's... >> It would just report the duration of the last-committed transaction for the session. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, May 4, 2024 at 12:54 AM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |