Re: Y2K conversion process

argosy22_at_my-deja.com wrote:
>
> HI all,
>
> We are now finally getting down to the Y2K issue!!
> (Not my decision to leave it until the last week!)
>

You mean, really now, it was management? Gee, some here want to blame the programmers.  

[snip]
> In the code, I have also found:
> to_char(to_date(ad_ed,'RR'),'YYYY'),
> - which will return a four digit year in character format.
>

Also windowed to proper century.  

> These fields for the year are basically used in
> SELECTs and joins. There are no calculations done with
> it, such as: year + 1, etc.
>

Killing performance BTW. You likely have a small database and you don't notice.  

> My initial thoughts for the conversion are:
>
> - change all the processes so that they use one of the
> above functions, ensuring that ALL fields with the varchar2
> year field are either 2 or 4 digits.
>

Proper fix would be to change them to a DATE datatype.  

> How we modify the two, and manage the change process is
> one big question.
>

Managing the changes? I brought that up a couple years ago, but SCM is unknown at many shops. Anyway, out of scope here, but you might want to toss the question out to news:comp.software.config-mgmt  

> So experienced people, does this sound like a good idea?
> Any other ideas?
> Does anyone knows of any websites that have overall
> outlines for dealing with the conversion?
>

In your case, see <http://www.monster.com/>

--
Are you ready for year MM?
The Mother of all Messes.
3 Days to go before 'Ignorance is bliss' is obsolete. news:comp.software.year-2000 Come for the signal, stay for the noise. Received on Tue Dec 28 1999 - 15:20:42 CST