Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Any reason to store time in 8-char field?
Message
From
01/05/2008 22:27:03
Thomas Ganss (Online)
Main Trend
Frankfurt, Germany
 
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 9 SP1
Miscellaneous
Thread ID:
01314637
Message ID:
01314687
Views:
7
>>I don't see why it should be 5 characters when 4 is enough. :)
>I get your point but I will still use 5. I just like the way this colon (:) looks in my field. Kind of like a double smile :)
>

I'd argue for keeping the seconds: Murphy says the sooner you ditch them, the sooner you will need them.
Calculating differences is another point to consider: if you keep your fields datetime this reduces risk of own errors.
If strapped for space (laaarge table with a couple of dozen such fields) I'd save seconds() in an integer field (recalc still easy), if really strapped for space (already nearing 2GB) I'd map minute count to a 2 byte char field.

my 0.02 EUR

thomas
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform