>>I gather from your description that the user created code is yours.
Not at all. *My* code would be the framework that is running these various bits of user submitted code.
>>1) Why will they not give you the access you request?
The most common answer is that my framework will only have a very limited amount of access, as in just access to one database, think low end commerical webhosting. It seems to be that it's inefficient / annoying to create a new table for every bit of user code that wants DB like functions, when just storing a pseudo db in some table in the database would be much cleaner.
>>2) You say it "Might need" database related functionality.
I have no clue what the user submitted code might need/do. It is beyond my control.
>>3) Your statement concerning "My immediate reaction is to hack a way around the rules".
This isn't employment related and any rules are merely guidelines for me. Perhaps they might be better called "wishes" instead of rules.
>>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
Actually according to a few of the people posting above you, the database I store inside another one will be able to emulate a 'real' database down to a very low level, including the nice sql calls, just not quite as efficiently as a 'real one' might. But then I'm not really looking in to storing a million row table inside another million row table.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.