Hey, I created a datalist with a nested repeater. In the nested repeater, I need to limit the amount of records shown (only 10 allowed). However, just limiting the second query into the dataset doesn't work, only grabs 10 records. So I need to figure out a way of only showing 10 results for each. Basically, let's say this is my setup:

Now I need to limit each category to 10 rows only. There are about 22 categories and about 10,000 results. Obviously I need to do my best to just limit it to 220 results, not 10,000!! Any help will be grateful. Thank you.

anyone have any suggestions? I suppose I can put a loop on and trully limit the amount per sub repeater, but that doesn't help the fact that my query will still return 10,000 results. This is especially worse as I am storing it in the cache to use in a dataset.

anyone? this will help tons.

I read through your question and could not quit understand the problem. How are you getting the data? from a database? why not restrict the number of records there? You could filter the dataset using the "DefaultView" row filter - http://msdn2.microsoft.com/en-us/lib...er(VS.71).aspx
. Send me your code and I will take a look.

It is dealt through a nested repeater. So the first repeater has no limits. It will show all 22-50 results needed. The second query (nested one), I would like to limit to 10 records per repeater. By limiting inside the query using LIMIT 10 or whatever, limits the results to all repeaters so that only 10 records are shown. So basically, this is what I want:

mmm...why are the nested repeater not restricted? Are you not using the ItemDataBound event to populate it? When doing so you could control how many records are process could you not?

yes i am using the itemdayabound method. could you explin please, and does it help against quering 10,000 rows when only 220 are needed?

Hi,

displaying any listed data in a web page is a three steps process (basically):

1. Getting the data from a database\source
2. processing the data
3. displaying the data

When you got the data in the first step you should get the minimum amount required. For the performance stand point there is no one answer; is it better to fetch all at once or go back and forth (in the item data bound) fetching the second level groups. It depends on the database size, network\location and number of sub groups queried in the item data bound. As a rule I probably would go with a very quick small query for the categories - something like a hundred results then query the database in the item data bound. Databases are better at querying data than .NET DataSets. However if the database is huge or far away from the web server I would think again.

To cut a long story short query the top level lets say school classes. Bind the DataTable to the list and in the Item Data Bound Query the database for each class students.

Another thing to consider is to show just the top level (classes in my example) and provide a link to the students what I call Card View. This way you do not need to bother with processing records the user might not be interested with (the down side is the need for the user to click twice to get the data).

if you still find it unclear send me your code and I will take a look...

Good Luck

Nope, makes perfect sense. The server is in the same building as the mysql server, so that is fine. I would just hate to tap the database.. 25 times instead of once.. you know? But if tapping the database 25 times and only retreving a total of 275 records compared to 10,000 (at the moment, but later above 100,000), the difference might be huge. Thanks.

Are you also getting the category information with your query result? If you are, you could select TOP 10 record of each category and use the foreach method to filter out the categories and populate your nested repeater.

In ASP.NET this seems a bit difficult, but in PHP this problem could be resolved without having to pre-filter your result.