The community database is the foundation for a set of social software applications. The primary focus is a user roster, a node roster, and a whuffie/mojo calculation and management system. The database is currently implemented in SQL tables on postgresql.

community database take two. March 2003 AdamShand, JerrittCollord, AaronBaer, DonPark, (insert your name here)

community database take three. February 2004

Wow, cool. I've probably seen this before but had forgotten about it. At the time of writing, the application described above has been mostly completed: see Adhocracy. Now that I've found this, I'm hoping to go back over it and add anything that's included here but missing there. All but one of the tables here ('addresses' - I once implemented it as 'locations' but then factored it out because it wasn't useful) has a direct parallel in Adhocracy: 'users' => 'users' (imagine that!), 'nodes' => 'interfaces', 'routers' => 'hosts' and 'communities' => 'zones'. (- KeeganQuinn 20060422)

Users Table

Description

Table Relationships

Fields

Table attributes - Cascade

Create Record

Delete Record

Node Table

Description

Table relationships

Fields

Check constraints:

Router table

Description

Table relationships

Fields

Interface table
Description

Table relationships

Fields

Addresses Table

Description Street address of users, nodes, etc.

Table Relationships

Fields

Community

Description

Fields

General table design notes

When indexing one table to another table, ie when table A contains a foreign key from table B, follow these practices:

System for getting at the data

Implementation


http://www.nodedb.com/ndbcom.dtd NodeDB.com xml schema...


[CategoryDocumentation]