On Sat, Feb 28, 2009 at 06:14:05PM -0800, jonwood wrote: > >So I would just rock it and not worry about it too much. If you're really > >that hard up on saving CPU cycles, they might be better gained elsewhere. > > I just like to be efficient and thought I'd check in to see if I was missing > anything. Looks like I'm not.
Storing dates with a two-digit year is... The deja vu, the deja vu! Why, oh why re-create y2k?! Premature optimization and all that. If INSERTs are rare and you're CPU-bound for SELECTs (because your DB fits in memory) then just INSERT raw time and pre-computed presentation forms. If you're not CPU-bound then don't worry. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
