Calendar fetch question

[edulid]

When are the fetch-operations in the calendar called? Are they called when you change the week by pressing the "next week" button?

[Isomorphic]

No - in current versions, Calendar views load all CalendarEvents on the first call to refreshEvents() - there is an existing plan to enable loadOnDemand features for Calendars, but these are not yet implemented.

We'll update here when progress happens on that.

[edulid]

ALL events? So if I have 1000 events, they will be all loaded during the first fetch?
I thought the calendar was implemented in a similar way like the listGrid, loading a maximum of 75 records per fetch by default.

[edulid]

Actually I see the following:

... y WHERE y.rowID BETWEEN 1 AND 75

so it seems that only the first 75 events are fetched. But I don't see any where clause taking the startdate/enddate into account. So if I have more than 75 events, the first 75 events will be loaded, ignoring the event dates? This doesn't seem correct if I understand correctly.
And when will the next 75 events be loaded ? Since the start/end-dates are not taken into account?

[edulid]

I just changed the date to 2018, and no new fetch was done, so I think I understand correctly.
As I already said, this seems to be incorrect, since the start/end-dates are ignored during the fetches.

[edulid]

If I have 449 events, I see:

y WHERE y.rowID BETWEEN 1 AND 75

and then:

y WHERE y.rowID BETWEEN 76 AND 449

So it seems to really fetch everything, in two rounds.
This is not scalable, why isn't it implemented like the ListGrids?
In a multi-user environment the 75 events are reached quickly.

[edulid]

Indeed, I took a look at my application in production, and there are already 200 events, after 2 weeks of production.

This means that we will reach very quickly 1000 events, 2000, 5000 events, etc, and they are always loaded all on startup?

[Isomorphic]

A follow up on this:
We misspoke on the previous post about adding this feature to 10.0.

In 10.1 and 10.0 we will be removing the 0-75 row range in the fetch which doesn't make sense in the absence of a date based fetching mechanism and is a bug.

More intelligent date based fetching is on the roadmap for 10.1, though we aren't guaranteeing an ETA.
(If this is essential for you, prioritizing it would be an eligable feature sponsorship).

In the meantime, if you need a more intelligent fetching approach, the right solution is to have application code perform a fetch against the dataSource and apply the result to the Calendar via setData. The dateChanged event can be used to react to the user changing views.

Sorry for the confusion, and we'll also remove the other post to avoid confusing other people browsing this thread

Regards
Isomorphic Software