Meta object model for relational data storage: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
imported>Hendrik Brummermann |
imported>Hendrik Brummermann introduction |
||
| Line 1: | Line 1: | ||
This article describes the idea of use a meta model to store RPClasses and RPObjects. It is not planned to actually do this anytime soon. |
|||
{{Inprogress}} |
|||
== Object Model of Marauroa == |
== Object Model of Marauroa == |
||
| Line 24: | Line 25: | ||
It consists of objects (4711 of type Player), values (43 for atk) and links (items in the bank_slot). Of cause there are some consistency conditions required. For example value.object.class <= value.attribute.class. |
It consists of objects (4711 of type Player), values (43 for atk) and links (items in the bank_slot). Of cause there are some consistency conditions required. For example value.object.class <= value.attribute.class. |
||
== Converting the Meta Model into a database structure == |
== Converting the Meta Model into a database structure == |
||
TODO: ... |
|||
A simple way to store generic object data in a relational database would be a meta model like the following. While it is nice nobody stepped up yet to implement it, which would be quite a bit of work with little gain. |
|||
CREATE TABLE class (id SERIAL, name VARCHAR); |
CREATE TABLE class (id SERIAL, name VARCHAR); |
||