Kragen Sitaker wrote:
So I hacked in a 'return 1' in _column_wanted, right underneath 'return 0
unless $tframe', and it seems to convince TableExtract to save the text
from all the columns, which is pretty much what I wanted, and even does
so without breaking anything else that I can see, except for presumably
using more time and space.
This is essentially what the 'keep_all_columns' feature would be doing
in the next release. Glad you weren't afraid to wade into the source!
I see that there's an 'umbrella' flag that
will also make it save everything, but it seems to inherit from table
to table...
The 'umbrella' flag pertains only to retaining subtables beneath the
targeted table, not the retained columns in the targeted table itself.
(though if you can target a table *containing* your target table...this
is getting into 'chains', though, which might be depracated soon since
it really needlessly complicates the logic of the module)
Do you think maybe you could add a million-and-third boolean flag to
have TableExtract save everything, in order to support applications like
this without wasting everybody's CPU and RAM?
You read my mind...
Matt
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
|
