<!-- 
RSS generated by JIRA (9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66) at Wed Feb 07 21:36:27 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>MongoDB Jira</title>
    <link>https://jira.mongodb.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>9.7.1</version>
        <build-number>970001</build-number>
        <build-date>13-04-2023</build-date>
    </build-info>


<item>
            <title>[CSHARP-309] Change argument type to long</title>
                <link>https://jira.mongodb.org/browse/CSHARP-309</link>
                <project id="10041" key="CSHARP">C# Driver</project>
                    <description>&lt;p&gt;In version 1.1 you changed type of return value of .Count() to long&lt;br/&gt;
So now we can have long-size count.&lt;/p&gt;

&lt;p&gt;but we can&apos;t skip some long-size items becasue MongoCursor&amp;lt;T&amp;gt;.SetSkip and MongoCursor&amp;lt;T&amp;gt;.SetLimit()&lt;br/&gt;
have the int arguments both.&lt;/p&gt;

&lt;p&gt;Please fix it.&lt;/p&gt;</description>
                <environment>Driver 1.1&lt;br/&gt;
Mongo 1.8.3</environment>
        <key id="21467">CSHARP-309</key>
            <summary>Change argument type to long</summary>
                <type id="4" iconUrl="https://jira.mongodb.org/secure/viewavatar?size=xsmall&amp;avatarId=14710&amp;avatarType=issuetype">Improvement</type>
                                            <priority id="3" iconUrl="https://jira.mongodb.org/images/icons/priorities/major.svg">Major - P3</priority>
                        <status id="6" iconUrl="https://jira.mongodb.org/images/icons/statuses/closed.png" description="The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.">Closed</status>
                    <statusCategory id="3" key="done" colorName="success"/>
                                    <resolution id="9">Done</resolution>
                                        <assignee username="robert@mongodb.com">Robert Stam</assignee>
                                    <reporter username="bug0r">Timofei Mironov</reporter>
                        <labels>
                            <label>driver</label>
                    </labels>
                <created>Wed, 24 Aug 2011 07:03:16 +0000</created>
                <updated>Thu, 20 Mar 2014 16:38:48 +0000</updated>
                            <resolved>Tue, 13 Sep 2011 16:01:32 +0000</resolved>
                                    <version>1.1</version>
                                                                        <votes>0</votes>
                                    <watches>0</watches>
                                                                                                                <comments>
                            <comment id="50673" author="rstam" created="Thu, 25 Aug 2011 13:41:59 +0000"  >&lt;p&gt;This algorithm for paging will only work it the total count of documents in the collection is not too large. If you know in advance that the count is reasonable, you could just change the code like this:&lt;/p&gt;

&lt;p&gt;var total = (int) cursor.Count(); // we know the count is small and will fit in an int&lt;br/&gt;
// etc...&lt;/p&gt;</comment>
                            <comment id="50643" author="bug0r" created="Thu, 25 Aug 2011 05:48:16 +0000"  >&lt;p&gt;Actualy not, we don&apos;t use large values for skip.&lt;br/&gt;
We meet it at the following case:&lt;/p&gt;

&lt;p&gt;long total = cursor.Count()&lt;br/&gt;
long pageCount = total/pagesize; // can be long&lt;br/&gt;
var skip = pageNum*pagesize;  // can be long if pageNum is long, 1 &amp;lt;= pageNum &amp;lt;= pageCount&lt;/p&gt;

&lt;p&gt;cursor.Find(...).SetSkip(skip);  // but argument is int&lt;/p&gt;

&lt;p&gt;I know that this situation looks like a joke, because of what is the paging where count of pages is long.&lt;br/&gt;
But it is possible by theory. For example if we process the items of big collections by 10 or 100 pieces.&lt;/p&gt;
</comment>
                            <comment id="50459" author="rstam" created="Wed, 24 Aug 2011 13:36:36 +0000"  >&lt;p&gt;I don&apos;t think it makes sense to use 64 bit values here. If you are skipping more than 2^31 results the cursor will timeout before ever returning the first document. And normally the limit value will be relatively small also, on the order of a few hundred or thousand, and certainly less than 2^31.&lt;/p&gt;

&lt;p&gt;What is your use case? Are you actually using large values for Skip and Limit?&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                                                                                                                                                                        <customfield id="customfield_10011" key="com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons">
                        <customfieldname>Backwards Compatibility</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10012"><![CDATA[Major Change]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                <customfield id="customfield_15850" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    <customfield id="customfield_12550" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2|hrh8hj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10558" key="com.pyxis.greenhopper.jira:gh-global-rank">
                        <customfieldname>Rank (Obsolete)</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>14174</customfieldvalue>
                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            </customfields>
    </item>
</channel>
</rss>