Subject | Re: [ib-support] Advice |
---|---|
Author | Jason Chapman (JAC2) |
Post date | 2002-02-13T08:24:36Z |
Definately do not store as date of birth if there are going to be a lot of
them.
Off the top of my head, if i wanted to store millions of birthdays and get
fastest retrieval when asking for birthdays within a period I would take the
day of year (always assume every year is a leap year or no year is a leap
year), and store this in an integer field (some testing i have done =>
smallints are slower). Stick an index on it and away you go.
For an even easier implementation if periods didn't have to be exact, but
roughish I would just take month*31+dayOfMonth as the hash.
My 2c worth without using any UDF's.
JAC.
""Luiz"" <cprmlao@...> wrote in message
news:017201c1b375$f5dcfa50$010aa8c0@......
them.
Off the top of my head, if i wanted to store millions of birthdays and get
fastest retrieval when asking for birthdays within a period I would take the
day of year (always assume every year is a leap year or no year is a leap
year), and store this in an integer field (some testing i have done =>
smallints are slower). Stick an index on it and away you go.
For an even easier implementation if periods didn't have to be exact, but
roughish I would just take month*31+dayOfMonth as the hash.
My 2c worth without using any UDF's.
JAC.
""Luiz"" <cprmlao@...> wrote in message
news:017201c1b375$f5dcfa50$010aa8c0@......
> I need advice about which the better choice to a column to storebirthdays,
> so that locating rows to birthdays in a period will be fast.
>
> Thanks,
> Luiz
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>