Brian. You don't like the idea. I get that.

If I proposed storing financial data with sales in one flat file. Customer numbers in another. Orders in yet another. And an index to all those files in yet another, you would be amongst the first people to advocate moving that data into a proper database.

The same holds true if it was an airline reservation system. Or a stock control application. Or almost any other set of data that had dependancies and relationships.

Why would I store that in something just to pull it out again? What structure is going to make that more simple?
The rest of the distribution looks the same, and the at the user level most people will not notice a difference.

You have read way to much into what I wrote--I made no proposals for what schema should be used, and you are showing no imagination for what could be done.

How about if the compiled bytecode was also stored the first time the module is used and subsequently that was returned.

How about if modules recorded the maximum or average sizes of arrays created by different calling applications and used that information to preextend their internals arrays accordingly on a per application basis.

How about ...

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco.
Rule 1 has a caveat! -- Who broke the cabal?

In reply to Re^4: CP6AN should be a database by BrowserUk
in thread Notion: CP6AN <strike>should</strike> could be a database by BrowserUk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.