Oracle PLSQL Language- P15

Chia sẻ: Thanh Cong | Ngày: | Loại File: PDF | Số trang:50

Thêm vào BST

Báo xấu

85
lượt xem 13
download

Download Vui lòng tải xuống để xem tài liệu đầy đủ

Tham khảo tài liệu 'oracle plsql language- p15', công nghệ thông tin, cơ sở dữ liệu phục vụ nhu cầu học tập, nghiên cứu và làm việc hiệu quả

Chủ đề:

Bình luận(0) Đăng nhập để gửi bình luận!

Lưu

Nội dung Text: Oracle PLSQL Language- P15

specification is: FUNCTION LAST_DAY (date_in IN DATE) RETURN DATE This function is useful because the number of days in a month varies throughout the year. With LAST_DAY, for example, you do not have to try to figure out if February of this or that year has 28 or 29 days. Just let LAST_DAY figure it out for you. Here are some examples of LAST_DAY: q Go to the last day in the month: LAST_DAY ('12-JAN-99') ==> 31-JAN-1999 q If already on the last day, just stay on that day: LAST_DAY ('31-JAN-99') ==> 31-JAN-1999 q Get the last day of the month three months after being hired: LAST_DAY (ADD_MONTHS (hiredate, 3)) q Tell me the number of days until the end of the month: LAST_DAY (SYSDATE) - SYSDATE 12.1.3 The MONTHS_BETWEEN function The MONTHS_BETWEEN function calculates the number of months between two dates and returns that difference as a number. The specification is: FUNCTION MONTHS_BETWEEN (date1 IN DATE, date2 IN DATE) RETURN NUMBER The following rules apply to MONTHS_BETWEEN: q If date1 comes after date2, then MONTHS_BETWEEN returns a positive number. q If date1 comes before date2, then MONTHS_BETWEEN returns a negative number. q If date1 and date2 are in the same month, then MONTHS_BETWEEN returns a fraction (a value between -1 and +1). q If date1 and date2 both fall on the last day of their respective months, then MONTHS_BETWEEN returns a whole number (no fractional component). q If date1 and date2 are in different months and at least one of the dates is not a last day in the month, MONTHS_BETWEEN returns a fractional number. The fractional component is Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
calculated on a 31-day month basis and also takes into account any differences in the time component of date1 and date2. Here are some examples of the uses of MONTHS_BETWEEN: q Calculate two ends of month, the first earlier than the second: MONTHS_BETWEEN ('31-JAN-1994', '28-FEB-1994') ==> -1 q Calculate two ends of month, the first later than the second: MONTHS_BETWEEN ('31-MAR-1995', '28-FEB-1994') ==> 13 q Calculate when both dates fall in the same month: MONTHS_BETWEEN ('28-FEB-1994', '15-FEB-1994') ==> 0 q Perform months_between calculations with a fractional component: MONTHS_BETWEEN ('31-JAN-1994', '1-MAR-1994') ==> - 1.0322581 MONTHS_BETWEEN ('31-JAN-1994', '2-MAR-1994') ==> - 1.0645161 MONTHS_BETWEEN ('31-JAN-1994', '10-MAR-1994') ==> - 1.3225806 If you detect a pattern here you are right. As I said, MONTHS_BETWEEN calculates the fractional component of the number of months by assuming that each month has 31 days. Therefore, each additional day over a complete month counts for 1/31 of a month, and: 1 divided by 31 = .032258065--more or less! According to this rule, the number of months between January 31, 1994 and February 28, 1994 is one -- a nice, clean integer. But to calculate the number of months between January 31, 1994 and March 1, 1994, I have to add an additional .032258065 to the difference (and make that additional number negative because in this case MONTHS_BETWEEN counts from the first date back to the second date. 12.1.4 The NEW_TIME function I don't know about you, but I am simply unable to remember the time in Anchorage when it is 3:00 P. M. in Chicago (and I really doubt that a lot of people in Anchorage can convert to Midwest U.S. time). Fortunately for me, PL/SQL provides the NEW_TIME function. This function converts dates (along with their time components) from one time zone to another. The specification for NEW_TIME Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
is: FUNCTION NEW_TIME (date_in DATE, zone1 VARCHAR2, zone2 VARCHAR2) RETURN DATE where date_in is the original date, zone1 is the starting point for the zone switch (usually, but not restricted to, your own local time zone), and zone2 is the time zone in which the date returned by NEW_TIME should be placed. The valid time zones are shown in Table 12.2. Table 12.2: Time Zone Abbreviations and Descriptions Time Zone Abbreviation Description AST Atlantic Standard Time ADT Atlantic Daylight Time BST Bering Standard Time BDT Bering Daylight Time CST Central Standard Time CDT Central Daylight Time EST Eastern Standard Time EDT Eastern Daylight Time GMT Greenwich Mean Time HST Alaska-Hawaii Standard Time Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
HDT Alaska-Hawaii Daylight Time MST Mountain Standard Time MDT Mountain Daylight Time NST Newfoundland Standard Time PST Pacific Standard Time PDT Pacific Daylight Time YST Yukon Standard Time YDT Yukon Daylight Time The specification of time zones to NEW_TIME is not case-sensitive, as the following example shows: TO_CHAR (NEW_TIME (TO_DATE ('09151994 12:30 AM', 'MMDDYYYY HH:MI AM'), 'CST', 'hdt'), 'Month DD, YYYY HH:MI AM') ==> 'September 14, 1994 09:30 PM' So, when it was 12:30 in the morning of September 15, 1994 in Chicago, it was 9:30 in the evening of September 14, 1994 in Anchorage. NOTE: By the way, I used TO_DATE with a format mask to make sure that a time other than the default of midnight would be used in the calculation of the new date and time. I then used TO_CHAR with another date mask (this one intended to make the output more readable) to display the date and time, because by default PL/SQL will not include the time component unless specifically requested to do so. 12.1.5 The NEXT_DAY function The NEXT_DAY function returns the date of the first day after the specified date which falls on the specified day of the week. Here is the specification for NEXT_DAY: Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
FUNCTION NEXT_DAY (date_in IN DATE, day_name IN VARCHAR2) RETURN DATE The day_name must be a day of the week in your session's date language (specified by the NLS_DATE_LANGUAGE database initialization parameter). The time component of the returned date is the same as that of the input date, date_in. If the day of the week of the input date matches the specified day_name, then NEXT_DAY will return the date seven days (one full week) after date_in. NEXT_DAY does not return the input date if the day names match. Here are some examples of the use of NEXT_DAY. Let's figure out the date of the first Monday and Wednesday in 1997 in all of these examples. q You can use both full and abbreviated day names: NEXT_DAY ('01-JAN-1997', 'MONDAY') ==> 06-JAN-1997 NEXT_DAY ('01-JAN-1997', 'MON') ==> 06-JAN-1997 q The case of the day name doesn't matter a whit: NEXT_DAY ('01-JAN-1997', 'monday') ==> 06-JAN-1997 q If the date language were Spanish: NEXT_DAY ('01-JAN-1997', 'LUNES') ==> 06-JAN-1997 q NEXT_DAY of Wednesday moves the date up a full week: NEXT_DAY ('01-JAN-1997', 'WEDNESDAY') ==> 08-JAN-1997 12.1.6 The ROUND function The ROUND function rounds a date value to the nearest date as specified by a format mask. It is just like the standard numeric ROUND function, which rounds a number to the nearest number of specified precision, except that it works with dates. The specification for ROUND is as follows: FUNCTION ROUND (date_in IN DATE [, format_mask VARCHAR2]) RETURN DATE The ROUND function always rounds the time component of a date to midnight (12:00 A.M.). The format mask is optional. If you do not include a format mask, ROUND rounds the date to the nearest day. In other words, it checks the time component of the date. If the time is past noon, then ROUND returns the next day with a time component of midnight. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
The set of format masks for ROUND is a bit different from those masks used by TO_CHAR and TO_DATE. (See Chapter 14, Conversion Functions, for more information on these functions.) The masks are listed in Table 12.3. These same formats are used by the TRUNC function, described later in this chapter, to perform truncation on dates. Table 12.3: Format Masks for ROUND and TRUNC Format Mask Rounds or Truncates to CC or SSC Century SYYY, YYYY, YEAR, SYEAR, YYY, YY, Year (rounds up to next year on July 1) or Y IYYY, IYY, IY, or I Standard ISO year Q Quarter (rounds up on the sixteenth day of the second month of the quarter) MONTH, MON, MM, or RM Month (rounds up on the sixteenth day, which is not necessarily the same as the middle of the month) WW Same day of the week as the first day of the year IW Same day of the week as the first day of the ISO year W Same day of the week as the first day of the month DDD, DD, or J Day DAY, DY, or D Starting day of the week HH, HH12, HH24 Hour Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
MI Minute Here are some examples of ROUND dates: q Round up to the next century: TO_CHAR (ROUND (TO_DATE ('01-MAR-1994'), 'CC'), 'DD- MON-YYYY') ==> 01-JAN-2000 q Round back to the beginning of the current century: TO_CHAR (ROUND (TO_DATE ('01-MAR-1945'), 'CC'), 'DD- MON-YYYY') ==> 01-JAN-1900 q Round down and up to the first of the year: ROUND (TO_DATE ('01-MAR-1994'), 'YYYY') ==> 01-JAN- 1994 ROUND (TO_DATE ('01-SEP-1994'), 'YEAR') ==> 01-JAN- 1995 q Round up and down to the quarter (first date in the quarter): ROUND (TO_DATE ('01-MAR-1994'), 'Q') ==> 01-APR-1994 ROUND (TO_DATE ('15-APR-1994'), 'Q') ==> 01-APR-1994 q Round down and up to the first of the month: ROUND (TO_DATE ('12-MAR-1994'), 'MONTH') ==> 01-MAR- 1994 ROUND (TO_DATE ('17-MAR-1994'), 'MM') ==> 01-APR- 1994 q Day of first of year is Saturday: TO_CHAR (TO_DATE ('01-JAN-1994'), 'DAY') ==> 'SATURDAY' So round to date of nearest Saturday for `01-MAR-1994': Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
ROUND (TO_DATE ('01-MAR-1994'), 'WW') ==> 26-FEB-1994 q First day in the month is a Friday: TO_CHAR (TO_DATE ('01-APR-1994'), 'DAY') ==> FRIDAY So round to date of nearest Friday from April 16, 1994: TO_CHAR ('16-APR-1994'), 'DAY') ==> SATURDAY ROUND (TO_DATE ('16-APR-1994'), 'W') ==> 15-APR-1994 TO_CHAR (ROUND (TO_DATE ('16-APR-1994'), 'W'), 'DAY') ==> FRIDAY In the rest of the examples I use TO_DATE in order to pass a time component to the ROUND function, and TO_CHAR to display the new time. q Round back to nearest day (time always midnight): TO_CHAR (ROUND (TO_DATE ('11-SEP-1994 10:00 AM', 'DD-MON-YY HH:MI AM'), 'DD'), 'DD-MON-YY HH:MI AM') ==> 11-SEP-1994 12:00 AM q Round forward to the nearest day: TO_CHAR (ROUND (TO_DATE ('11-SEP-1994 4:00 PM', 'DD-MON-YY HH:MI AM'), 'DD'), 'DD-MON-YY HH:MI AM') ==> 12-SEP-1994 12:00 AM q Round back to the nearest hour: TO_CHAR (ROUND (TO_DATE ('11-SEP-1994 4:17 PM', 'DD-MON-YY HH:MI AM'), 'HH'), 'DD-MON-YY HH:MI AM') ==> 11-SEP-1994 04:00 PM 12.1.7 The SYSDATE function The SYSDATE function returns the current system date and time as recorded in the database. The time component of SYSDATE provides the current time to the nearest second. It takes no arguments. The specification for SYSDATE is: Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
FUNCTION SYSDATE RETURN DATE SYSDATE is a function without parameters; as a result, it looks like a system-level variable and programmers tend to use it as if it is a variable. For example, to assign the current date and time to a local PL/SQL variable, you would enter the following: my_date := SYSDATE; However, SYSDATE is not a variable. When you use SYSDATE, you are calling a function, which executes underlying code. NOTE: In Oracle Version 6 and the earliest releases of the Oracle Server, when you called SYSDATE, PL/SQL issued an implicit cursor to the database to get the current date and time, as follows: SELECT SYSDATE FROM dual; Because this is no longer the case, you do not need to be as concerned about extra calls to SYSDATE as you would have in earlier releases. 12.1.8 The TRUNC function The TRUNC function truncates date values according to the specified format mask. The specification for TRUNC is: FUNCTION TRUNC (date_in IN DATE [, format_mask VARCHAR2]) RETURN DATE The TRUNC date function is similar to the numeric FLOOR function discussed in Chapter 13, Numeric, LOB, and Miscellaneous Functions. Generally speaking, it rounds down to the beginning of the minute, hour, day, month, quarter, year, or century, as specified by the format mask. TRUNC offers the easiest way to retrieve the first day of the month or first day of the year. It is also useful when you want to ignore the time component of dates. This is often the case when you perform comparisons with dates, such as the following: IF request_date BETWEEN start_date AND end_date THEN ... The date component of date_entered and start_date might be the same, but if your application does not specify a time component for each of its dates, the comparison might fail. If, for example, the user enters a request_date and the screen does not include a time component, the time for request_date will be midnight or 12:00 A.M. of that day. If start_date was set from SYSDATE, Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
however, its time component will reflect the time at which the assignment was made. Because 12:00 A.M. comes before any other time of the day, a comparison that looks to the naked eye like a match might well fail. If you are not sure about the time components of your date fields and variables and want to make sure that your operations on dates disregard the time component, TRUNCate them: IF TRUNC (request_date) BETWEEN TRUNC (start_date) AND TRUNC (end_date) THEN ... TRUNC levels the playing field with regard to the time component: all dates now have the same time of midnight (12:00 A.M.). The time will never be a reason for a comparison to fail. Here are some examples of TRUNC for dates (all assuming a default date format mask of DD-MON- YYYY): q Without a format mask, TRUNC sets the time to 12:00 A.M. of the same day: TO_CHAR (TRUNC (TO_DATE ('11-SEP-1994 9:36 AM', 'DD- MON-YYYY HH:MI AM')) ==> 11-SEP-1994 12:00 AM q Trunc to the beginning of the century in all cases: TO_CHAR (TRUNC (TO_DATE ('01-MAR-1994'), 'CC'), 'DD- MON-YYYY') ==> 01-JAN-1900 TO_CHAR (TRUNC (TO_DATE ('01-MAR-1945'), 'CC'), 'DD- MON-YYYY') ==> 01-JAN-1900 q Trunc to the first of the current year: TRUNC (TO_DATE ('01-MAR-1994'), 'YYYY') ==> 01-JAN- 1994 TRUNC (TO_DATE ('01-SEP-1994'), 'YEAR') ==> 01-JAN- 1994 q Trunc to the first day of the quarter: TRUNC (TO_DATE ('01-MAR-1994'), 'Q') ==> 01-JAN-1994 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
TRUNC (TO_DATE ('15-APR-1994'), 'Q') ==> 01-APR-1994 q Trunc to the first of the month: TRUNC (TO_DATE ('12-MAR-1994'), 'MONTH') ==> 01-MAR- 1994 TRUNC (TO_DATE ('17-MAR-1994'), 'MM') ==> 01-APR- 1994 In the rest of the examples I use TO_DATE to pass a time component to the TRUNC function, and TO_CHAR to display the new time: q Trunc back to the beginning of the current day (time is always midnight): TO_CHAR (TRUNC (TO_DATE ('11-SEP-1994 10:00 AM', 'DD-MON-YYYY HH:MI AM'), 'DD'), 'DD-MON-YYYY HH:MI AM') ==> 11-SEP-1994 12:00 AM TO_CHAR (TRUNC (TO_DATE ('11-SEP-1994 4:00 PM', 'DD-MON-YYYY HH:MI AM'), 'DD'), 'DD-MON-YYYY HH:MI AM') ==> 11-SEP-1994 12:00 AM q Trunc to the beginning of the current hour: TO_CHAR (TRUNC (TO_DATE ('11-SEP-1994 4:17 PM', 'DD-MON-YYYY HH:MI AM'), 'HH'), 'DD-MON-YYYY HH:MI AM') ==> 11-SEP-1994 04:00 PM Previous: 11.2 Character Oracle PL/SQL Next: 12.2 Date Function Function Examples Programming, 2nd Edition Examples 11.2 Character Function Book Index 12.2 Date Function Examples Examples The Oracle Library Navigation Copyright (c) 2000 O'Reilly & Associates. All rights reserved. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Previous: 12.1 Date Chapter 12 Next: 13. Numeric, LOB, Function Descriptions Date Functions and Miscellaneous Functions 12.2 Date Function Examples This section contains more detailed examples of some of the functions summarized in this chapter. 12.2.1 Customizing the Behavior of ADD_MONTHS As noted earlier, if you pass a day to ADD_MONTHS which is the last day in the month, PL/SQL always returns the last day in the resulting month, regardless of the number of actual days in each of the months. While this may work perfectly well for many, if not most, Oracle installations, I have encountered at least one company in the insurance industry that definitely cannot use ADD_MONTHS the way it works by default. At this site, if I am on the 28th day of February and shift forward a month, I need to land on the 28th of March -- not the 31st of March. What's a programmer to do? The best solution is to write your own version of ADD_MONTHS that performs the way you want it to, and then use it in place of ADD_MONTHS. The following example shows a new_add_months function. It always lands you on the same day in the month, unless the original day does not exist in the new month, in which case the day is set to the last day in the new month. This code uses the LAST_DAY function to see if the original date falls on the last day of that month: /* Filename on companion disk: addmths.sf */ CREATE OR REPLACE FUNCTION new_add_months (date_in IN DATE, months_shift IN NUMBER) RETURN DATE IS /* Return value of function */ return_value DATE; /* The day in the month */ day_of_month VARCHAR2(2); Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
/* The month and year for the return value */ month_year VARCHAR2(6); /* The calculated end of month date */ end_of_month DATE; BEGIN return_value := ADD_MONTHS (date_in, months_shift); /* Is original date the last day of its month? */ IF date_in = LAST_DAY (date_in) THEN /* Pull out the day number of the original date */ day_of_month := TO_CHAR (date_in, 'DD'); /* Grab the month and year of the new date */ month_year := TO_CHAR (return_value, 'MMYYYY'); /* Combine these components into an actual date */ BEGIN end_of_month := TO_DATE (month_year || day_of_month, 'MMYYYYDD'); /* || Return the earliest of (a) the normal result of ADD_MONTHS || and (b) the same day in the new month as in the original month. */ return_value := LEAST (return_value, end_of_month); EXCEPTION WHEN OTHERS THEN NULL; END; END IF; /* Return the shifted date */ RETURN return_value; END new_add_months; Take a look at the difference between ADD_MONTHS and new_add_months: ADD_MONTHS ('31-JAN-1995', 1) ==> 28-FEB-1995 new_add_months ('31-JAN-1995', 1) ==> 28-FEB-1995 ADD_MONTHS ('28-FEB-1994', 2) ==> 30-APR-1994 new_add_months ('28-FEB-1994', 2) ==> 28-APR-1995 Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
The above function can be used in a PL/SQL program like the following: IF new_add_months (order_date, 3) > SYSDATE THEN ship_order; END IF; If you want new_add_months to also accept the two arguments in either date-number or number-date order, you need to place the function inside a package and then overload the function definition, as shown below; see Chapter 16, Packages, for more information on constructing packages and overloading module definitions. PACKAGE date_pkg IS FUNCTION new_add_months (date_in IN DATE, months_shift IN NUMBER) RETURN DATE; FUNCTION new_add_months (months_shift IN NUMBER, date_in IN DATE) RETURN DATE; END; If you are using PL/SQL Release 2.1 or beyond, you can use this substitute for ADD_MONTHS in your SQL DML statements, as well as your PL/SQL programs: SELECT new_add_months (SYSDATE, 3) FROM dual; A final observation: the unexpected behavior of ADD_MONTHS for the last day in a month demonstrates once again that it is always a good idea to test both your programs and the programs of others at their limits. Don't assume that a program will work in any particular fashion until you test it. In this case, if the program shifts dates by months, then be sure to test for the end and beginning of months. 12.2.2 Using NEW_TIME in Client-Server Environments One issue to keep in mind with SYSDATE is that it will always reflect the date and time on the server and not on the individual client workstation or computer (unless, of course, your workstation is also the server). This may not be an issue when all machines are located in the same general vicinity, but when you have a server in New York and a client in Iowa, the times will definitely not match up. This is a more difficult problem to resolve. You can use the NEW_TIME date function to convert the date and time returned by SYSDATE to the actual date and time in the client's location. To do this you need to know the time zones in each of these locations. The best way to be sure the time zones are available is to store them in a Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
configuration table; the zones may then be read into some kind of global variables when an application is initiated. In PL/SQL, you would do this with package variables. Note that this example relies heavily on the package structure, which is explained in Chapter 16. In the following examples, I will store the client and server time zone values directly in PL/SQL variables and provide a way to change them if necessary. I will then build a function called system_date, which replaces the SYSDATE function. The objectives of this function are twofold: 1. Keep to a minimum the number of times that SYSDATE is called. 2. Adjust the time automatically to account for time zone changes. The tz package shown below provides a set of procedures and functions to manage both the system date and the client and server time zones. Users of the package can access the package data only through the functions (retrieval) and the procedures (change values). The main module in the package is system_date; its specification follows: FUNCTION system_date (refresh_in IN VARCHAR2 := 'NOREFRESH', server_time_zone IN VARCHAR2 := server, client_time_zone IN VARCHAR2 := client) RETURN DATE; This package-based version of SYSDATE takes up to three parameters: refresh_in If you need the current time or want to update the global current date value, then you really do want SYSDATE to be called again. If you refresh, then SYSDATE is used to update the package globals. server_time_zone The time zone of the server; the default is the packaged value. client_time_zone The time zone of the client; the default is the packaged value. The tz package relies on the following global variables inside the package to keep track of the current date/time and the default client and server time zones: system_date_global DATE := SYSDATE; client_tz VARCHAR2(3) := 'AST'; server_tz VARCHAR2(3) := 'PST'; Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
The very first time the system_date function is called, the package will be loaded into memory and these variables assigned their default values. I can now call system_date using both of the default configuration time zones -- and I will not get a new time computed each time I do so: IF tz.system_date BETWEEN '15-JAN-1994' AND '22-JAN-1994' THEN ... END IF; Or I can override the default time zones with Greenwich Mean and Newfoundland Standard times, also requesting a refresh of the time: current_date := tz.system_date ('REFRESH', 'GMT', 'NST'); If you do not want to have to specify the package name, tz, in front of the system_date function name, you can create a standalone stored procedure of the same name which, in effect, hides the package ownership: FUNCTION system_date (refresh_in IN VARCHAR2 := 'NOREFRESH', server_time_zone VARCHAR2 := tz.server, client_time_zone VARCHAR2 := tz.client) RETURN DATE IS BEGIN RETURN tz.system_date (refresh_in, server_time_zone, client_time_zone); END; The following sections contain the code for the specification and body of the tz package. 12.2.2.1 The time zone package specification /* Filename on companion disk:tz.spp */ PACKAGE tz IS /* Return the client timezone */ FUNCTION client RETURN VARCHAR2; /* Return the server timezone */ FUNCTION server RETURN VARCHAR2; /* || Retrieve system date. Can ask to refresh the value Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
|| from the database and also over-ride the default || time zones, just as you would with NEW_TIME. */ FUNCTION system_date (refresh_in IN VARCHAR2 := 'NOREFRESH', server_time_zone IN VARCHAR2 := server, client_time_zone IN VARCHAR2 := client) RETURN DATE; /* Change the client timezone */ PROCEDURE set_client (tz_in IN VARCHAR2); /* Change the server timezone */ PROCEDURE set_server (tz_in IN VARCHAR2); END tz; 12.2.2.2 The time zone package body /* Filename on companion disk: tz.spp */ PACKAGE BODY tz IS /* The actual "global" variables stored in the package */ system_date_global DATE := SYSDATE; client_tz VARCHAR2(3) := 'AST'; server_tz VARCHAR2(3) := 'PST'; FUNCTION client RETURN VARCHAR2 IS BEGIN RETURN client_tz; END; FUNCTION server RETURN VARCHAR2 IS BEGIN RETURN server_tz; END; FUNCTION system_date (refresh_in IN VARCHAR2 := 'NOREFRESH', server_time_zone IN VARCHAR2 := tz.server, client_time_zone IN VARCHAR2 := tz.client) RETURN DATE IS BEGIN Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
/* Update the system date global if requested */ IF UPPER (refresh_in) = 'REFRESH' THEN tz.system_date_global := SYSDATE; END IF; /* Use NEW_TIME to shift the date/time */ RETURN NEW_TIME (system_date_global, server_time_zone, client_time_zone); END; PROCEDURE set_client (tz_in IN VARCHAR2) IS BEGIN assert (valid_time_zone (tz_in )); client_tz := tz_in; END; PROCEDURE set_server (tz_in IN VARCHAR2) IS BEGIN assert (valid_time_zone (tz_in )); server_tz := tz_in; END; PROCEDURE assert( condition_in IN BOOLEAN ) IS BEGIN IF NOT condition_in THEN RAISE VALUE_ERROR; END IF; END; FUNCTION valid_time_zone( time_zone_in IN VARCHAR2 ) RETURN BOOLEAN IS validation_tz VARCHAR2(3) := 'EST'; -- a valid time zone validation_date DATE; invalid_time_zone EXCEPTION; PRAGMA EXCEPTION_INIT(invalid_time_zone, -1857); BEGIN validation_date := NEW_TIME( SYSDATE, time_zone_in, validation_tz ); RETURN TRUE; Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
EXCEPTION WHEN invalid_time_zone THEN RETURN FALSE; END; END tz; Previous: 12.1 Date Oracle PL/SQL Next: 13. Numeric, LOB, Function Descriptions Programming, 2nd Edition and Miscellaneous Functions 12.1 Date Function Book Index 13. Numeric, LOB, and Descriptions Miscellaneous Functions The Oracle Library Navigation Copyright (c) 2000 O'Reilly & Associates. All rights reserved. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.
Previous: 12.2 Date Chapter 13 Next: 13.2 LOB Function Function Examples Descriptions 13. Numeric, LOB, and Miscellaneous Functions Contents: Numeric Function Descriptions LOB Function Descriptions Miscellaneous Function Descriptions This chapter describes three sets of PL/SQL functions: the functions that manipulate numbers; the functions used to initialize large object (LOB) values; and a variety of miscellaneous functions which you will find useful. These sets of functions are listed in Tables Table 13.1 through Table 13.3. Table 13.1: The Built-in Numeric Functions Name Description ABS Returns the absolute value of the number. ACOS Returns the inverse cosine. ASIN Returns the inverse sine. ATAN Returns the inverse tangent. ATAN2 Returns the result of the tan2 inverse trigonometric function. CEIL Returns the smallest integer greater than or equal to the specified number. Please purchase PDF Split-Merge on www.verypdf.com to remove this watermark.