Opasnet Base: Difference between revisions

From Opasnet
Jump to navigation Jump to search
Line 180: Line 180:
|}
|}
|}
|}
====Contents of selected tables====
{|
|
{| {{prettytable}}
|+ Table objtype
! id!! objtype
|----
|| 1|| Variable
|----
|| 2|| Study
|----
|| 3|| Method
|----
|| 4|| Assessment
|----
|| 5|| Class
|----
|| 6|| Index
|----
|| 7|| Nugget
|----
|| 8|| Encyclopedia article
|----
|| 9|| Run
|----
|}
|
{| {{prettytable}}
|+ Table acttype
! id|| acttype
|----
|| 1|| Start object
|----
|| 2|| Finish assessment
|----
|| 3|| Update formula
|----
|| 4|| Upload data (replace)
|----
|| 5|| Upload data (append)
|----
|| 6|| Review scope
|----
|| 7|| Review definition
|----
|| 8|| Add object info
|----
|}
|}


==See also==
==See also==

Revision as of 12:01, 24 January 2012



This page is about the Opasnet Base 2 -database.

Question

How to improve the existing Opasnet Base? Following issues of Opasnet Base 1 must be resolved:

  • Opasnet Base 1 structure makes filtering by location very slow on big data
  • Opasnet Base 1 structure is perhaps unnecessarily complex = queries are hard to adapt and read
  • MySQL is not ideal for storing huge amounts of data, or at least this is how we assume?
  • MySQL tables have fixed column types = difficult to store data objects with varying types of indices into one data table
  • Multiple languages (localization) not supported

Answer

MySQL is good on relations but weak on dynamic big data. Let's keep the basic "scaffold" in MySQL and store the big data (locations and results) into noSQL-base. After few days of research the best candidate for noSQL-base seems to be MongoDB. Combining relational MySQL and non-relational MongoDB will be the foundation for the new Opasnet Base 2.

Table structure in the database

All tables

acts
Uploads, updates, and other actions
Field Type Null Extra Key
id int(10) unsigned NO auto_increment PRI
type ENUM('initial','replace','append') NO
who varchar(50) NO
comments varchar(250) YES
time timestamp NO
temp_id int(10) unsigned NO MUL
acts_locs
Locations of an act
Field Type Null Extra Key
actobj_id int(10) unsigned NO PRI
loc_id int(10) unsigned NO PRI
acts_objs
Acts of an objects
Field Type Null Extra Key
id int(10) unsigned NO auto_increment PRI
act_id int(10) unsigned NO MUL
obj_id int(10) unsigned NO MUL
dat_id int(10) unsigned NO MUL
unit varchar(64) YES
objs
Object information (all objects)
Field Type Null Extra Key
id int(10) unsigned NO auto_increment PRI
ident varchar(20) NO UNI
name varchar(200) NO
type ENUM('variable','study','method','assessment','class','nugget','encyclopedia') NO
page int(10) unsigned NO
wiki_id tinyint(3) unsigned NO
lang char(2) NO
inds
Indices
Field Type Null Extra Key
id int(10) unsigned NO auto_increment PRI
ident varchar(20) NO UNI
name varchar(200) NO
page int(10) unsigned NO
wiki_id tinyint(3) unsigned NO
locs
Location information
Field Type Null Extra Key
id int(10) unsigned NO auto_increment PRI
std_id int(10) unsigned NO MUL
obj_id_i int(10) unsigned NO MUL
location varchar(100) NO
roww mediumint(8) unsigned NO
description varchar(150) NO





wikis
Wiki information
Field Type Null Extra Key
id tinyint(3) NO PRI
url varchar(255) NO
wname varchar(20) NO

See also