RE: Thoughts in /* standardized SQL remarks */
- From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxxxxx>
- To: <post.ethan@xxxxxxxxx>, "Oracle Discussion List" <oracle-l@xxxxxxxxxxxxx>
- Date: Fri, 17 Mar 2006 15:50:13 -0500
Not a bad idea, but, if you use DBMS_APPLICATION_INFO, that may be a
more generic and appropriate interface.
--
Mark J. Bobak
Senior Oracle Architect
ProQuest Information & Learning
"Exception: Some dividends may be reported as qualified dividends but
are not qualified dividends. These include:
* Dividends you received on any share of stock that you held for less
than 61 days during the 121-day period that began 60 days before the
ex-dividend date. The ex-dividend date is the first date following the
declaration of a dividend on which the purchaser of a stock is not
entitled to receive the next dividend payment. When counting the number
of days you held the stock, include the day you disposed of the stock
but not the day you acquired it. See the examples below. Also, when
counting the number of days you held the stock, you cannot count certain
days during which your risk of loss was diminished. See Pub. 550 for
more details."
--IRS, Form 1040-A Instruction Booklet, Line 9b: Qualified Dividends
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Ethan Post
Sent: Friday, March 17, 2006 3:45 PM
To: Oracle Discussion List
Subject: Thoughts in /* standardized SQL remarks */
Reading through some very long and complicated SQL trace files today, I
find I frequently have to go grep the code to try to find out where the
SQL originated from. Do you think a comment in the SQL should be
standardized for our development staff?
SELECT /* module, about, date modified */
what are your thoughts?
Other related posts:
