Database

Using the notecards in object inventory as a way to parametrize a script is quite cumbersome. It would be useful to define a database object taht could be queried by

string result = llQueryDB(string dbname, string criteria)

where dbname is the DB object in the same inventory of script

o.O before anyone who knows what your talking about, and can do something about it, enough attention from laymen needs to be brought upon a subject. Speak english man. WTF did you just say?

Windows programs can put parameters in files or in the windows registry for recall or manipulation. No equivalent system exists in lsl.

The OP is suggesting LL operate a db to store similar values in sl for objects.

Considering LL's priorities, it will be a long time before this feature is implemented. Meanwhild, you cn use http and a web server to maintain long term storage.

The trouble with actual database implementations is that languages such as SQL are VERY text heavy, queries and large-ish results will require rather large strings, not to mention the parsing of a multi-row/column result! The issue as a result is that the usage of such a system is very limited. An in-house language would be required for fetching single values to keep memory usage down, remember we only have 16k.

Possibilities like this exist however, as you can create a 'database' script and query this with link-messages. This would be perfectly good if all you want to store are simple variables, e.g; objectName = "My Object"

There are easier ways to do this. Requires a bit of scripting and some ASP, Perl or PHP knowledge. Ofcourse this will be quite a bit of data...

You create a DB script on a webserver. Listening function and outputting function.
use llHTTPRequest(); to send your query.
for example:
llHTTPRequest('http://example.com/?query=SELECT * FROM....'); The whitespaces may be filled with %20 automatically (not sure) If they're not, fill them in yourself. %20 is 'web' for space.

The website queries the database, and outputs in a list format you create. Perhaps a csv style (comma separated values).
use http_response listener to process this. Interpret the input and BOOM! You got your functional database.
This is just a VERY basic framework and can easily be expanded.