Oracle if updating field srilankan badu poto
i don't even see a primary key a date field has but one part -- it is just 7 bytes.
You can attribute "meaning" to different bytes (one means year, one hour and so on) but at the end of the day -- a date is a date, just like a number is a number. I apologize Tom, I only listed the Primary Key attributes for my example to avoid confusion...
I assume if I use TRUNC function, optimizer may not be able to use Indexes for retrieving result sets. There are many problems when having a date field as a primary key: a) Exact fetch is practically impossible to do.
b) Referential integrity is very, very hard to accomplish.
saint louis regional airport has a military and a civilian portion that are both uniquely identified by the FAA, even though it is the same geophysical location).
Fiscal Year Identifier is self explanatory as a four digit representation of a fiscal year (i.e. Report Identifier is a sequence that is generated for each new report generated in a fiscal period, and is set to zero each year on October 1st.
I do have issues with a DATE being the primary key.
What I suggest is to: First, if you can, do not choose a date; choose number(8) or number(12) and when you update the field, use to_number(sysdate,'yyyymmdd') Second, to enforce a foreign key, when you update the father in a transaction, save the date/time entered in a temporary variable, and when updating the child, use the same variable. Or is this one of the Great Myths of Database Design? January 28, 2002 - am UTC Well, my followup to their comments are: a) exact fetch is practically impossible to do....Before, the report identifiers were character representations of a sequence, that would reset at the end of the fiscal year.The customer has not expressed an interest in deviating from this method of fiscal identifier generation.And then the only avenue is to use a formatted string that includes just the date component, such as "to_char (sysdate, 'MMDDYYYY')", as part of the primary key, instead of the date. I think this is what was being attempted to be explained in the comments above. IF you are using SYSDATE as a primary key value AND you are inserting more than one record per second BY DEFINITION you cannot use SYSDATE as the primary key value Is there anything wrong with using a column of type DATE as a primary key? Can there be a logical problem with it in your application? Firstly, thank you for your knowledge and your perspective on our issues.(patience as well...) I am presently in debate with a colleague and want your opinion.