Hi,
I am currently having a problem migrating data from my previous scheduler to your scheduler. My problem is mostly on the performance issue I am facing.
That is why I would like to know, how does telerik scheduler manage data loading?
for example
my scheduler uses recurrence function and it is bind to a sqldatasource using early binding method. and the sqldatasource statement is "SELECT * FROM myTABLE WHERE EVENTTYPE = 5"
and i set the selected date of my scheduler to 2008 Oct 06.
now here is my question,
1. does it load every data where the eventtype = 5 and store it on the buffer on the first run, and only shows data which is in the date range of my scheduler in this case 2008 Oct 05 until 2008 Oct 11,
2. or doest it automatically load data where the eventtype = 5 and startdate > 2008 Oct 05 and startdate < 2008 Oct 11?
3. if you use the 2nd type of data loading, how do you handle data that start before 2008 Oct 05, but recurs until 2008 Oct 12?
How does the scheduler optimised the data loading that's cover the occurence events to display the desire result set out for day view, week view and month view. My concerns is that the performance may drop as the pointer need to start from record 1 to last record in order to handle the occurence events.
I am currently having a problem migrating data from my previous scheduler to your scheduler. My problem is mostly on the performance issue I am facing.
That is why I would like to know, how does telerik scheduler manage data loading?
for example
my scheduler uses recurrence function and it is bind to a sqldatasource using early binding method. and the sqldatasource statement is "SELECT * FROM myTABLE WHERE EVENTTYPE = 5"
and i set the selected date of my scheduler to 2008 Oct 06.
now here is my question,
1. does it load every data where the eventtype = 5 and store it on the buffer on the first run, and only shows data which is in the date range of my scheduler in this case 2008 Oct 05 until 2008 Oct 11,
2. or doest it automatically load data where the eventtype = 5 and startdate > 2008 Oct 05 and startdate < 2008 Oct 11?
3. if you use the 2nd type of data loading, how do you handle data that start before 2008 Oct 05, but recurs until 2008 Oct 12?
How does the scheduler optimised the data loading that's cover the occurence events to display the desire result set out for day view, week view and month view. My concerns is that the performance may drop as the pointer need to start from record 1 to last record in order to handle the occurence events.