As you analyze your ideas and organize your thoughts, you will use MUDzilla
to store your work.
is based on relational database
where a collection of database tables
assigned relationships between one another based on data they share in common. Each table is divded into
), and each record
is divided into fields
Within each field lies a value
which represents a single piece of information regarding the Multiverse
A snapshot of a MUDzilla
database represents a moment in time, where the sum total of all values in all records
in all tables indicates the current state
of the simulation.
MUDzilla uses the Paradox 7 format,
a flat-file database where the relationships between tables within the database are maintained as part
of MUDzilla software applications.
The link between our software and the underlying database is managed by the
Borland Database Engine, which
provides a Structured Query Language (SQL)
interface. SQL is a powerful data manipulation language that extends the scalability of MUDzilla
to other database platforms, such as Oracle and
SQL Server. In time, the Paradox format will cease to meet the needs of
a large simulation. SQL ensures that when the time comes to scale up to a database server, the
overall logic of MUDzilla will be preserved.
A MUDzilla database is the static part of a simulation, a vast store of knowledge which, taken together,
represents the past. Not until the simulation is started does the database transition into
a reflection of the present. To make this leap, the simulation needs to represent information
known only while the simulation is active, the simulation's short-term memory. This is the exact purpose and function
of objects, which have both
persistent parts, information which is stored in the database, and memory parts,
knowledge which only exists during the lifetime of the object. MUDzilla enforces the
Nothing Unreal Exists
axiom by ensuring that all data is manipulated within the context of the object model.