1. Question: Year 2000 bug and impact on databases, database applications, and database management
I am currently preparing a graduate paper on the impact of the Year 2000 (Y2K) bug
on databases, database applications, and database management. Specific areas of
interest to me and the group to whom it will be presented are:
Knowledge Discovery and Data Mining,
OO Databases, and
Text & Document Databases.
If you work with one or more of the above, and have specific examples of how the
Y2K bug is going to affect you, the database(s), or the way you do work, and how
you (or others) are specifically addressing the problem, would you please respond
either on the NG or via e-mail (address below, too)?
If you don't know about Y2K, but can at least give me an idea of how data with date
fields or date information is used in any of the particular specialties above,
whether your particular area of databasing uses primarily two-digit date fields,
and the potential impact of having the year field "roll-over" to "00", that would
be just as good.
Any and all assistance will be most helpful. Thanks,
University of Kansas
2. Stored Procedure speed issue
3. SQL Question on Year 1900 's vs Year 2000's
4. Sum question
5. Year 2000 compliant 4gl code
6. trouble with a decode statement
7. Year 2000 and recompilation of 4GL forms
8. postgresql does seqscan instead of using an existing
9. Informix 4GL and year 2000 problems/ramblings
10. Weblogic year 2000 bug!!
11. Weblogic year 2000 bug?
12. The "year 2000 bug"
13. Forms 3 Year 2000 Bug