Re: [teiid-dev] "MaxResultRows" in the Connectors

Ramesh: I completely support the idea of eliminating the 10,000 MaxResultRows default. It should default to "unlimited". (It's not like RDBMSes constrain their users in such a fashion.) Cheers, ------- Paul Nittel JBoss Sr. Quality Assurance Engineer Red Hat, Inc. 314-336-2907 (81-62907) Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ ----- Original Message ----- From: "Ramesh Reddy" <rareddy(a)redhat.com&gt; To: teiid-dev(a)lists.jboss.org Sent: Wednesday, March 17, 2010 10:32:00 AM GMT -06:00 US/Canada Central Subject: [teiid-dev] "MaxResultRows" in the Connectors Teiid supports a property called "MaxResultRows" in Connector properties, which defaults to 10,000 rows. The expected behavior of this is to throw an exception when user queries more than 10,000 rows through this connector. However, this default behavior seems like a exceptional condition than normal behavior expected by user any time. This *was* designed more for the development time aid than the runtime. Here is an example of community user tripping over it. http://community.jboss.org/message/532560#532560 I propose, we change the default value of this property to zero (0) that means the "MaxResultRows" will be set to "unlimited" in the default scenario. If user requires to restrict max rows they can *explicitly* set a value that they are comfortable with. Any objections? Thanks. Ramesh.. _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev _______________________________________________ teiid-dev mailing list teiid-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/teiid-dev