From: Sahananda (J. W. <sah...@wi...> - 2012-06-04 13:01:06
|
Hi Lee, good to hear from you again. I hope your are well! I have been thinking about this some more, and I think that the low level structure Mark is aiming for where you have an array where the first element is metadata and the rest is data will make any high level wrapper around it difficult to code and probably rather inefficient (assuming I have understood correctly what he is aiming for). To dig a single column out of a dataset would then require something like this: do row over rows~section(2) -- skip the metadata say row[rows[1]~index('fieldname')] end Which feels very awkward to me There is a Rexx precedent in the way that stems are used to return results from external functions where stem.0 holds the metadata (number of results) and the rest of the stem the data. I never like using that, and my opinion fwiw is that it would be better to create a structure where the data and metadata are kept separate even at the low level design. just my two more cents worth Jon On 4 June 2012 12:47, Lee Peedin <le...@sa...> wrote: > Mark, lets assume your table structure is something like: > firstname > lastname > address > city > state > zip > > Now lets assume your sql query was simply: > select * from table > > Both your and Jon's query would work fine UNTIL the point where it's > determined that we now need a > middleinitial column between firstname and lastname. The beauty of SQL is > that column can be > inserted and the integrity of the data is not harmed. > > HOWEVER, if your case of using an array of arrays, every statement in > every script that expected the > lastname to be the 2nd column to be returned would have to now be changed > to the 3rd column. > > But, hey, what do I know. > > Lee > > On 6/3/2012 11:24 PM, Mark Miesfeld wrote: > > On Sun, Jun 3, 2012 at 2:33 PM, Sahananda (Jon) Wolfers < > sah...@wi... > > <mailto:sah...@wi...>> wrote: > > > > I know that you're thinking about the lower level now, but consider > an array of directories as > > then one can refer to columns by name. I know there are some > interfaces (like windows ADODBC, > > and I seem to recall JDBC was a bit like this) where you have to > work really hard to fetch each > > row, and then you have to work really hard to fetch each field from > the row. It feels a whole > > lot more rexxish to me to be able to say > > > > osql~exec(myQuery) > > > > do row over osql~rows > > if row['name'] = 'Smith' then do ... end > > end > > > > Well, I think the above is close to what I have now: > > results = osql~exec(myQuery) > > do row over results > > if row[2] = 'Smith' then do ... end > > end > > What I was saying was that it wouldn't be too hard at this point to let > the user specify if the > > returned result set was an array of arrays or an array of directory > objects. > > -- > > Mark Miesfeld > > > > > > > ------------------------------------------------------------------------------ > > Live Security Virtual Conference > > Exclusive live event will cover all the ways today's security and > > threat landscape has changed and how IT managers can respond. Discussions > > will include endpoint security, mobile security and the latest in malware > > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 7192 (20120603) __________ > > > > The message was checked by ESET NOD32 Antivirus. > > > > http://www.eset.com > > > > > > > > > > _______________________________________________ > > Oorexx-devel mailing list > > Oor...@li... > > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > > > > > > > > __________ Information from ESET NOD32 Antivirus, version of virus > signature database 7192 (20120603) __________ > > > > The message was checked by ESET NOD32 Antivirus. > > > > http://www.eset.com > > > > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Oorexx-devel mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > |