I gather from your description that the user created code is yours.

A couple of questions come to mind.

1) Why will they not give you the access you request?
Could it be space constraints, system performance, uncomfortable with your design?

2) You say it "Might need" database related functionality.
If your design is this incomplete, it is no surprise the DBA will not change the schema.

3) Your statement concerning "My immediate reaction is to hack a way around the rules".
If this is employment related, stop, drop and roll, because if your hack cooks a production database, some one will be waving the ugly stick in your direction.

If this is school related - Same stick, less cash value risk.

I know the rules ain't no fun, but if you are in an environment where the rules exist, and you can not change them, there is a reason.

Difficulties I see with the proposed solution from a programming stand point: the database you store in another database (dysiad) will not act like a database to your program, you will not be able to order data, read data selectively or any of the other cool things a database can do for you. The best I can see (since you are not allowed to use disk either) is that you will store the dysiad in the main database, slurp it into memory as an array, perhaps, manipulate it, and write it back to the main database as a complete block..

I am willing to learn why and how this would be useful, but am also interested in why you are under these constraints.

No flame intended, but I have done corporate recoveries from people intellegent enough to bypass the rules in some clever way.

dageek

If I am convinced that the rules souldn't apply to me, they probably were written for me.

In reply to Re: Databases with in databases by johndageek
in thread Databases with in databases by BUU

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.