good ideas. The spread sheet trick hadn't occurred to me. I think I'll go that route since it keeps things user readable
thank you for your thoughts, all. regards, Adam On Thu, Apr 22, 2010 at 2:51 AM, Oliver Peters <oliver....@web.de> wrote: > > Adam DeVita <adev...@...> writes: > > > > [...] > > > > If I have to generate the date dimension on my own, I'm hoping to use > > something like > > create table date_dimension ( > > [Dateid] integer primary key, > > [Real_Year] int , > > [Month_name] text, > > [Day] int , > > [QuarterNumber] int, > > [DayofWeek_name] text, > > [dayofYear] int, > > [epoch_day] int, > > [julian_day] int > > ); > > > > [...] > > Why don't you simply use a spreadsheet program like OpenOfice Calc or Excel > to > prepare the table data for your fixed timespan (2010 - 2030) and import the > whole thing? > > Would be a work of a few minutes ;-) > > greetings > Oliver > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- VerifEye Technologies Inc. 905-948-0015x245 7100 Warden Ave, Unit 3 Markham ON, L3R 8B5 Canada _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
