Sorry, I pressed Send by mistake. I try again.
>
>> Regarding using a table for record sets, someone else has brought that
>> up. I'm thinking about adding it to the different record format types.
>> Exactly how does that work? Each individual record is a single table
>> object with the column names the indexes in the table? Each record is put
>> into a ? Put into a table with the index the record number?
>>
>>
>
>From my point of view (others may disagree) the option would be a new
OO_ARRAY_OF_TABLES that would be just like OF_ARRAYS and OF_DIRECTORIES.
The question is whether the performance issue can be solved, if not I guess
OO_ARRAY_OF_ARRAYS is the only way out. This option is slightly more coding
demanding than for example a table. Here is a simple example of using a
table:
resultRows = db~exec("SELECT * FROM TBL1", .true)
loop row over resultRows~allItems
name = row["NAME"]
pfone = row["PHONE"]
end
But this is just how the current ARRAYS_OF_DIRECTORIES works really.
I hope this helps
Staffan
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
