>>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.