Framework database - Revision history

Ktrueman: clean up

2009-07-17T17:10:30Z

clean up

Ktrueman at 19:53, 7 May 2009

2009-05-07T19:53:46Z

Ktrueman at 19:53, 7 May 2009

2009-05-07T19:53:16Z

Ktrueman: New page: A database is required by the framework for persistent storage; not suprisingly it is called the framework database. It is used to store the configuration, states and status of the system....

2009-05-07T19:52:15Z

New page: A database is required by the framework for persistent storage; not suprisingly it is called the framework database. It is used to store the configuration, states and status of the system....

New page

A database is required by the framework for persistent storage; not suprisingly it is called the framework database. It
is used to store the configuration, states and status of the system. The framework database’s schema is imposed on
client and is considered an API. This means that it is subjected to the same rules as any Telcoridges API. The schema
was written in XML so the SQL generation script can be generated using simple XSL sheets. This was done to make
it easy to switch DBMS since the SQL data definition language is not always portable. This also makes it possible
to generate visual representations of the database using another XSL sheet and Graphviz. Of course the framework
must support the DBMS, fortunately we support ODBC so the framework supports almost any database through that
interface. In the future we will also add support for some DBMS natively.

This database was created and designed for the Web OAMP.

== Caveats ==

*Note that the division is purely hierarchical and both the databases can be hosted on the same database.
*There is no restriction on the the DBMS of the framework database except that we must support it.

← Older revision		Revision as of 19:53, 7 May 2009
Line 15:		Line 15:
	*Note that the division is purely hierarchical and both the databases can be hosted on the same database.		*Note that the division is purely hierarchical and both the databases can be hosted on the same database.
	*There is no restriction on the the DBMS of the framework database except that we must support it.		*There is no restriction on the the DBMS of the framework database except that we must support it.
		+
		+
		+	----
		+
		+	Return to the Toolpack [[User Guide]]

@@ Line 1: / Line 1: @@
-A database is required by the framework for persistent storage; not surprisingly it is called the framework database. It
+A database is required by the framework for persistent storage; not surprisingly it is called the framework database. It is used to store the configuration, states and status of the system. The framework database’s schema is imposed on client and is considered an [[API|application programming interface (API)]]. This means that it is subjected to the same rules as any TelcoBridges API. The schema was written in [[XML]] so the SQL generation script can be generated using simple XSL sheets. This was done to make it easy to switch [[DBMS]] since the SQL data definition language is not always portable. This also makes it possible to generate visual representations of the database using another XSL sheet and Graphviz. Of course the framework
-is used to store the configuration, states and status of the system. The framework database’s schema is imposed on
+must support the DBMS, fortunately we support [[ODBC]] so the framework supports almost any database through that interface. In the future we will also add support for some DBMS natively.
 client and is considered an application programming interface (API). This means that it is subjected to the same rules as any TelcoBridges API. The schema
 was written in XML so the SQL generation script can be generated using simple XSL sheets. This was done to make
 it easy to switch DBMS since the SQL data definition language is not always portable. This also makes it possible
 to generate visual representations of the database using another XSL sheet and Graphviz. Of course the framework
 must support the DBMS, fortunately we support ODBC so the framework supports almost any database through that
 interface. In the future we will also add support for some DBMS natively.
-This database was created and designed for the Web OAMP.
+This database was created and designed for the [[Toolpack]] Web OAMP.