Timothy R Myers | "More people would learn from their
Frederick, MD USA | mistakes if they weren't so busy
Opps, don't know where it went...
>Timothy R Myers | "More people would learn from their
>Frederick, MD USA | mistakes if they weren't so busy
Ok, I don't claim to be the originator of this idea, but it was used
extensively at an older work site. They had a flat file engine, which
for our purposes we can dub 'ffeng'. It was written in c, kept in a
public directory. When presented with standard input and a series
of flags, it could process the data by sorting on any key in the record,
or merely present the field of the record(s) needed. It could sort
individual fields too. The program was written so that it could be
easily accessed as the 'shell' of a script, so that you could easily
code data in the form:
# This data file is also a script
# we'll make a database of /etc/passwd info as an example
# records start here
comment "Fred Flintstone"
comment "Barney Rubble"
# end of file
It was a fairly powerful technique. The neat thing is that the data
become self documenting and the data also become a script for searching
on the data. The data are human readable and compact.
I'm curious if something like that is out there now, in the public
domain. If not, are there coded flat file engines that would be
readily adaptable to supporting this kind of coding technique? My
preference would be an engine in 'c', and no one has to adopt
my particular nomenclature, but I certainly could use a tool like
this, when I'm having to do common Unix systems administration tasks
on multiple systems in heterogenous environments where the number of
records to be handled is small, say, less than a couple thousand.
Sent via Deja.com http://www.deja.com/
Before you buy.