Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> ad hoc sysdate changes for debugging purposes

ad hoc sysdate changes for debugging purposes

From: Xeno Campanoli <v-xenoc_at_microsoft.com>
Date: Wed, 22 Apr 1998 13:26:05 -0500
Message-ID: <6hlk51$ic3@news.microsoft.com>


We are testing usage of date ranges which depend at runtime on the current OS date/time, and we would like to test these for many date-time combinations; basically boundary points and midrange points, so three date-time combinations at least for each day of the week. I can't help but think there must be a method in Oracle to set the date-time found in "sysdate" before running an application so that we can make our checks effectively without having to inconvenience the machine's system administrator into jerking around the actual OS date/time. Please can someone suggest some effective debugging methods for imposing ad hoc sysdate values to an Oracle job or copy or running thread or whatever so that subsequent applications can be made to think sysdate is that ad hoc value chosen rather than the actual one. Thank you.

Sincerely, Xeno Campanoli

--
The opinions expressed in this message are my own personal views and do not reflect the official views of the Microsoft Corporation. Received on Wed Apr 22 1998 - 13:26:05 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US