Subject | Re: [firebird-support] DB design best practices - which solutionis faster? |
---|---|
Author | Peter Faulks |
Post date | 2010-11-19T14:26:23Z |
I'm still not 100% sure what it is you are doing....
Sounds like you need a separate table then. Join the two on a integer
primary key - use create generator and select gen_id() to create a
sequence. (it is always generally a good thing to make primary keys
meaningless)
When does a reminder expire? would you then delete it from the table?
Why would a reminder be set for after the event?
Sounds like you need a separate table then. Join the two on a integer
primary key - use create generator and select gen_id() to create a
sequence. (it is always generally a good thing to make primary keys
meaningless)
When does a reminder expire? would you then delete it from the table?
Why would a reminder be set for after the event?
On Fri, 2010-11-19 at 14:15 +0100, Zd wrote:
> Hello Set,
>
> The problem is that reminders can be set x hours/days/weeks etc.
> before or after an event. Thus I can't say that I only check for
> reminders 1 week before or after the event.
>
> I'm also worried about querying of UserIDs, ie.: SELECT ... FROM
> Calendar WHERE UserID = ...
>
> If I have a table with 200.000 records and only 4 UserIDs, how slow is
> that going to be?
>
> Thanks,
> Zd
>