Feature Req/Issue: Allow column order in custom sprocs to not have to be in specific order...

[GoogleCodeExporter]

Given a table with columns A,B,C...  In order for a custom procedure to 
generate a method that returns a TList<T> rather than a DataSet, you need to 
return all the columns -- and in the expected order... 

If you're getting back a TList<T> return type but have a change to the custom 
procedure where the correct # of columns are returned with the right/expected 
column names -- but in an order different from what was originally generated 
against... you get errors in the Fill() operation often (i.e. casting int to 
string, encountering DBNull when not expected, etc)...  

This appears to be because of the use of ordinal positions (reader[0]) versus 
name (reader["A"]) in the Fill() operation... 

I imagine this is done for performance reasons, but having been the tech 
lead/architect on multiple projects using NetTiers I can tell you it has proven 
to be problematic -- especially for developers coming onto a project that don't 
know the nuances of working with NetTiers.

I would like to see this requirement 'relaxed' to be more tolerant of ordering. 
Obviously the correct number and name of columns must be returned... And to 
alleviate the performance considerations, why not cache the lookup of column 
name to ordinal position and then use that cached meta-data from that point 
forward... best of both worlds...

Original issue reported on code.google.com by bh...@questis.com on 17 Sep 2010 at 4:30

[GoogleCodeExporter]

Hello,

This sounds fair enough and is exactly what CodeSmith is doing in some of the 
other frameworks. I'll talk with jeff on this and get this changed in a nightly 
or in 3.0.

Thanks
-Blake Niemyjski

Original comment by bniemyjski on 21 Sep 2010 at 12:14

• Changed state: Investigating

[GoogleCodeExporter]

Reviewing old items I logged to follow-up and check for progress...

Original comment by bh...@questis.com on 8 Jun 2011 at 5:20

[GoogleCodeExporter]

Hello,

We are actively working on .netTiers 3.0 and got a lot done last week with 3.0. 
We will be putting a preview out this summer and are looking over all issues. 
Please note that the "active" open source .netTiers team is small and we work 
on this in our free time. We could really use any and all extra hands in 
developing 3.0. Are you interested?

Thanks
-Blake Niemyjski

Original comment by bniemyjski on 5 Jul 2011 at 2:57