comment on

Well I would view that as either a header issue, that is on the file level, or as a data record specification issue. I should say though that I tried to stay away from the data as a whole as I'm more concerned with the strucuture of the container and not so much what it contains.

In other words, in some situations support for change records is required, but how its implemented I would think would require a lot of contextual analysis that can't be broadly generalized. Although please feel free to outline your thoughts on the subject, its not really something thats come up for me regularly, in fact only once really.

---
$world=~s/war/peace/g

In reply to Re^2: Thoughts on designing a file format. by demerphq
in thread Thoughts on designing a file format. by demerphq

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


more useful options
	PerlMonks