Using a DATE field, or 3 fields (year, month, day) simulating a date?! Which one??

Bijan

Hi,

I had a program that I was working on for some month and now that it's finished, I feel somehow guilty about it! Because I'm living in Iran and our date system is totally different from jeorgian date system (for example our year is 1382 currently!), so, instead of using a date field in mySql, I used 3 INT fields: Year, Month and Day. That I could easily insert my dates without the fear of day light savings and stuff like that. But now that I had 2 functions for converting between our date system and jeorgian date system (and vice versa) I'm wondering if it's worth it to go and rewrite the tables. I just wana know if I encounter some performance problems in the future or better to say if it's going to be very slow when the number of records in my DB grows. Should I change it or it's just ok the way that it is?!

Thanks for your help

dopp

perhaps there is a conversion function that turns a gregorian date into one of your calender?

I find working with dates is ugly business, good luck!

Bijan

Originally posted by dopp
perhaps there is a conversion function that turns a gregorian date into one of your calender?

I find working with dates is ugly business, good luck!

Lol, yeah, it's ugly business!

You're right, I have those functions (Jalali to Gregorian and vice versa) now and I was wondering if it's worth it that I go back and change all the code working with these functions, and of course changing the tables and stuff.

Still looking for new suggestions!
bijan