UniTextus.net: A work in progress!

For now the biggest point of disscussion is the database design. Because the entire application is based on a database, it would be a huge mistake to scamp this design. The idea is simple, every piece of text is essentially the same, this is why we (plan to) have a table with two rows only, an identification-row, and a row with the text. Depending on the kind of entry (blogpost, wiki-page, etc) other data needs to be saved that’s what we use the table metadata for. For this, you could think about title, order (forumcategories e.g.) and the type
of contents (forumthread, forumcategory, blogpost, etc). We’ll also support tagging, because
it will happen most often that tags are used more than once,
we’ve chosen to use a many to many relationship for these with the entries. Then there’s the table what it’s all about, the table that defines the relationship
between 2 or more entries here

Someone also wondered why have fixed ‘types’ for each entry. We basically don’t because you can add just as many type-metadata’s per entry as one wants.

The proposal

Tags: database, design, entry, relation

This entry was posted on Wednesday, December 26th, 2007 at 1:48 pm and is filed under UniTextus. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.