On Jan 16, 2008 5:40 PM, Robert Locke <[EMAIL PROTECTED]> wrote: > > So in my case since I have a lot of functions that deal with dates i > > would need at least two int columns to replace the date column. Is > > this the widely accepted industry practice? > > I can't speak authoritatively on industry practice but we've been able > to get away with just using indexed datetime columns without the need > to create (additional) "int" columns...
How about using epochs in an int column to express dates, then using either your database's datetime converter builtins or your language's own converters? Cheers, Zakame -- Zak B. Elep || http://zakame.spunge.org [EMAIL PROTECTED] || [EMAIL PROTECTED] || [EMAIL PROTECTED] 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D _________________________________________________ Philippine Linux Users' Group (PLUG) Mailing List [email protected] (#PLUG @ irc.free.net.ph) Read the Guidelines: http://linux.org.ph/lists Searchable Archives: http://archives.free.net.ph
