Databases - Revision history

Jukeboksi: Juboxi moved page Database to Databases: pluralization is rational as per content

2016-08-27T10:53:20Z

Juboxi moved page Database to Databases: pluralization is rational as per content

← Older revision		Revision as of 10:53, 27 August 2016
(No difference)

Jukeboksi: moving == Factors affecting database systems selections == to systems selections

2016-08-27T10:45:23Z

moving == Factors affecting database systems selections == to systems selections

← Older revision		Revision as of 10:45, 27 August 2016
Line 12:		Line 12:
	For more options and information see the '''[[w:Database model\|Wikipedia article on database models]]'''.		For more options and information see the '''[[w:Database model\|Wikipedia article on database models]]'''.
	----		----

	~~== Factors affecting database systems selections ==~~

	* [[Copyleft]] 'free to modify' and 'free in cost' software is strongly preferred over other solutions.
	* Minimal modifications required could be another preference as that means maintenance of the chosen solution is minimized in that aspect.

	== Relational databases ==		== Relational databases ==

Jukeboksi: /* Useful resources for database related matters */ + A very good SPARQL tutorial Cambridge Semantics

2016-08-27T10:29:27Z

Useful resources for database related matters: + A very good SPARQL tutorial Cambridge Semantics

← Older revision		Revision as of 10:29, 27 August 2016
Line 86:		Line 86:
	== Useful resources for database related matters ==		== Useful resources for database related matters ==
	* [http://swat.cse.lehigh.edu/projects/lubm/ Lehigh University Benchmark] may be useful in evaluating [[w:semantic query\|semantic query]] performance		* [http://swat.cse.lehigh.edu/projects/lubm/ Lehigh University Benchmark] may be useful in evaluating [[w:semantic query\|semantic query]] performance
			* [http://www.cambridgesemantics.com/semantic-university/sparql-by-example A very good SPARQL tutorial Cambridge Semantics]

Jukeboksi: starting on == Useful resources for database related matters == + w:semantic query| performance evaluation tool

2016-08-27T08:37:15Z

starting on == Useful resources for database related matters == + w:semantic query performance evaluation tool

← Older revision		Revision as of 08:37, 27 August 2016
Line 2:		Line 2:

	''' Types of databases of interest being evaluated'''		''' Types of databases of interest being evaluated'''
	* [[#Relational databases\|Relational ~~database~~]] provided by a [[w:~~RDBMS~~\|RDBMS]] and queried with [[w:SQL\|SQL]]. Track-proven ~~technology~~.		* [[#Relational databases\|Relational databases]] provided by a [[w:Relational Database Management System\|RDBMS]] and queried with [[w:SQL\|SQL]]. Track-proven technolog applied, since the early 70's.
	* [[#NoSQL databases\|NoSQL]]-type databases, ( "Not Only SQL" or have your pick on the other supposed significations ) variates include among others:		* [[#NoSQL databases\|NoSQL]]-type databases, ( "Not Only SQL" or have your pick on the other supposed significations ) variates include among others:
	** [[#Subject-predicate-object databases\|Subject-predicate-object databases]] are implemented by [[w:graph databases\|graph databases]], specialized native [[w:Triplestore\|triplestore]]s and piggy-packing solutions that use an RDBMS to store and query the triplets and the networks they compose.		** [[#Subject-predicate-object databases\|Subject-predicate-object databases]] are implemented by [[w:graph databases\|graph databases]], specialized native [[w:Triplestore\|triplestore]]s and piggy-packing solutions that use an RDBMS to store and query the triplets and the networks they compose.
Line 82:		Line 82:
	''' Lists of object databases '''		''' Lists of object databases '''
	* [[w:Object_database#Timeline\|Wikipedia's list of object databases by publication date.]]		* [[w:Object_database#Timeline\|Wikipedia's list of object databases by publication date.]]

			----
			== Useful resources for database related matters ==
			* [http://swat.cse.lehigh.edu/projects/lubm/ Lehigh University Benchmark] may be useful in evaluating [[w:semantic query\|semantic query]] performance

Jukeboksi: fix introductory paragraph links to be internal, Wikipedia ones are there. fix headings once again, this time pluralizing

2016-08-27T08:29:36Z

fix introductory paragraph links to be internal, Wikipedia ones are there. fix headings once again, this time pluralizing

← Older revision		Revision as of 08:29, 27 August 2016
Line 1:		Line 1:
	'''This article is about choice of database models and implementations.'''		'''This article is about choice of database models and implementations.'''

	''' Types of databases of interest'''		''' Types of databases of interest being evaluated'''
	* [[w:Relational ~~database~~\|Relational database]] provided by a [[w:RDBMS\|RDBMS]] and queried with [[w:SQL\|SQL]]. Track-proven technology.		* [[#Relational databases\|Relational database]] provided by a [[w:RDBMS\|RDBMS]] and queried with [[w:SQL\|SQL]]. Track-proven technology.
	* [[w:NoSQL]], ( "Not Only SQL" or have your pick on the other supposed significations ) variates:		* [[#NoSQL databases\|NoSQL]]-type databases, ( "Not Only SQL" or have your pick on the other supposed significations ) variates include among others:
	** [[w:Subject-predicate-object databases]] are implemented by [[w:graph databases\|graph databases]], specialized native [[w:Triplestore\|triplestore]]s and piggy-packing solutions that use an RDBMS to store and query the triplets and the networks they compose.		** [[#Subject-predicate-object databases\|Subject-predicate-object databases]] are implemented by [[w:graph databases\|graph databases]], specialized native [[w:Triplestore\|triplestore]]s and piggy-packing solutions that use an RDBMS to store and query the triplets and the networks they compose.
	** [[w:Graph databases\|Graph databases]] would intuitively appear more advanced than using RDF-triplet composed semantic networks but are not much different on the outside. Both jump through the same hoops but with different efficiency and grace.		** [[#Graph databases\|Graph databases]] would intuitively appear more advanced than using RDF-triplet composed semantic networks but are not much different on the outside. Both jump through the same hoops but with different efficiency and grace.
	** [[w:Object ~~database~~\|Object ~~database~~]]s are old but on the rise with NoSQL-based thinking and the modern needs, like leanness, real-time need and scaleability for which the other solutions might be too limiting.		** [[#Object databases\|Object databases]] are old but on the rise with NoSQL-based thinking and the modern needs, like leanness, real-time need and scaleability for which the other solutions might be too limiting.

	All of these may be used to store semantic data though advantages and disadvantages vary depending on task at hand.		All of these may be used to store semantic data though advantages and disadvantages vary depending on task at hand.
Line 18:		Line 18:
	* Minimal modifications required could be another preference as that means maintenance of the chosen solution is minimized in that aspect.		* Minimal modifications required could be another preference as that means maintenance of the chosen solution is minimized in that aspect.

	== Relational ~~database~~ ==		== Relational databases ==

	Relational databases work by storing data in [[w:Table (database)\|tabular form]] where [[w:column (database)\|columns]] represent data items of predetermined type and [[w:row (database)\|rows]] represent the values each "item" has. Relational databases are accessed mainly with [[w:SQL\|SQL]] ( Structured Query Language ). However the RDBMS converts that into [[w:relational algebra\|relational algebra]] and optimizes that and the relational algebra query actually returns the result table that has those columns and rows you requested.		Relational databases work by storing data in [[w:Table (database)\|tabular form]] where [[w:column (database)\|columns]] represent data items of predetermined type and [[w:row (database)\|rows]] represent the values each "item" has. Relational databases are accessed mainly with [[w:SQL\|SQL]] ( Structured Query Language ). However the RDBMS converts that into [[w:relational algebra\|relational algebra]] and optimizes that and the relational algebra query actually returns the result table that has those columns and rows you requested.
Line 41:		Line 41:
	----		----

	=== Subject-predicate-object ~~database~~ ===		=== Subject-predicate-object databases ===
	Subject-predicate-object databases basically construct [[w:semantic]] networks from interlinked atomic units called a [[w:triplet]] so they are not fundamentally different from graph databases in functionality and utility offered.		Subject-predicate-object databases basically construct [[w:semantic]] networks from interlinked atomic units called a [[w:triplet]] so they are not fundamentally different from graph databases in functionality and utility offered.

Line 65:		Line 65:
	----		----

	=== Graph ~~database~~ ===		=== Graph databases ===
	A [[w:graph database\|graph database]] stores and queries [[w:Graph (abstract data type)\|graphs]].		A [[w:graph database\|graph database]] stores and queries [[w:Graph (abstract data type)\|graphs]].

Line 78:		Line 78:
	----		----

	=== Object ~~database~~ ===		=== Object databases ===
	{{Q\|An object database stores complex data and relationships between data directly, without mapping to relational rows and columns, and this makes them suitable for applications dealing with very complex data.\|Wikipedia\|[[w:Object_database#Comparison_with_RDBMSs\|functional difference between object and relational databases]]}}		{{Q\|An object database stores complex data and relationships between data directly, without mapping to relational rows and columns, and this makes them suitable for applications dealing with very complex data.\|Wikipedia\|[[w:Object_database#Comparison_with_RDBMSs\|functional difference between object and relational databases]]}}
	''' Lists of object databases '''		''' Lists of object databases '''
	* [[w:Object_database#Timeline\|Wikipedia's list of object databases by publication date.]]		* [[w:Object_database#Timeline\|Wikipedia's list of object databases by publication date.]]

Jukeboksi: link to w:database models

2016-08-26T21:29:42Z

link to w:database models

← Older revision		Revision as of 21:29, 26 August 2016
Line 10:		Line 10:
	All of these may be used to store semantic data though advantages and disadvantages vary depending on task at hand.		All of these may be used to store semantic data though advantages and disadvantages vary depending on task at hand.

			For more options and information see the '''[[w:Database model\|Wikipedia article on database models]]'''.
	----		----

Jukeboksi: expanding on the ==== Relevant subject-predicate-object database powered systems to interoperate with ====

2016-08-26T21:23:22Z

expanding on the ==== Relevant subject-predicate-object database powered systems to interoperate with ====

← Older revision		Revision as of 21:23, 26 August 2016
Line 50:		Line 50:

	==== Relevant subject-predicate-object database powered systems to interoperate with ====		==== Relevant subject-predicate-object database powered systems to interoperate with ====
	* [[Semantic MediaWiki]]		* '''[[Semantic MediaWiki]]''' is system for inputting and querying semantic data within the MediaWiki and it is implemented as extension(s).
	* [[DBpedia]]		* '''[[DBpedia]]''' the original structured data harvesting effort for the MediaWiki wikis
	* [[Wikidata]]		* '''[[Wikidata]]''' is effort by the [[Wikimedia Foundation]] since 2012 to provide a central storage for data items instead of manually replicating it in various language versions


	==== Things to consider in selection of triplestore ====		==== Things to consider in selection of triplestore ====

Jukeboksi: added quick internal navigation to == NoSQL ==

2016-08-26T20:51:09Z

added quick internal navigation to == NoSQL ==

← Older revision		Revision as of 20:51, 26 August 2016
Line 34:		Line 34:
	{{Q\|Honestly 'Not Only SQL' sounds best from what I've read.\|Lowest Troll\|[[w:NoSQL\|NoSQL]]}}		{{Q\|Honestly 'Not Only SQL' sounds best from what I've read.\|Lowest Troll\|[[w:NoSQL\|NoSQL]]}}
	All the following database types can be considered variations of NoSQL.		All the following database types can be considered variations of NoSQL.
			* [[#Subject-predicate-object database\|Subject-predicate-object database]]
			* [[#Graph database\|Graph databases]]
			* [[#Object database\|Object database]]

	----		----

Jukeboksi: + note about all the databases presented being able to store semantic data (maybe not efficiently, all of them)

2016-08-26T20:47:47Z

+ note about all the databases presented being able to store semantic data (maybe not efficiently, all of them)

← Older revision		Revision as of 20:47, 26 August 2016
Line 7:		Line 7:
	** [[w:Graph databases\|Graph databases]] would intuitively appear more advanced than using RDF-triplet composed semantic networks but are not much different on the outside. Both jump through the same hoops but with different efficiency and grace.		** [[w:Graph databases\|Graph databases]] would intuitively appear more advanced than using RDF-triplet composed semantic networks but are not much different on the outside. Both jump through the same hoops but with different efficiency and grace.
	** [[w:Object database\|Object database]]s are old but on the rise with NoSQL-based thinking and the modern needs, like leanness, real-time need and scaleability for which the other solutions might be too limiting.		** [[w:Object database\|Object database]]s are old but on the rise with NoSQL-based thinking and the modern needs, like leanness, real-time need and scaleability for which the other solutions might be too limiting.

			All of these may be used to store semantic data though advantages and disadvantages vary depending on task at hand.

	----		----

Jukeboksi: moved info to its own heading == Factors affecting database systems selections ==

2016-08-26T20:36:14Z

moved info to its own heading == Factors affecting database systems selections ==

← Older revision		Revision as of 20:36, 26 August 2016
Line 1:		Line 1:
	This article is about choice of database models and implementations.		'''This article is about choice of database models and implementations.'''

	[[Copyleft]] free to modify and free in cost software is strongly preferred over other solutions. Minimal modifications required could be another preference as that means maintenance of the chosen solution is minimized in that aspect.

	''' Types of databases of interest'''		''' Types of databases of interest'''
Line 11:		Line 9:

	----		----

			== Factors affecting database systems selections ==

			* [[Copyleft]] 'free to modify' and 'free in cost' software is strongly preferred over other solutions.
			* Minimal modifications required could be another preference as that means maintenance of the chosen solution is minimized in that aspect.

	== Relational database ==		== Relational database ==
Line 70:		Line 73:
	=== Object database ===		=== Object database ===
	{{Q\|An object database stores complex data and relationships between data directly, without mapping to relational rows and columns, and this makes them suitable for applications dealing with very complex data.\|Wikipedia\|[[w:Object_database#Comparison_with_RDBMSs\|functional difference between object and relational databases]]}}		{{Q\|An object database stores complex data and relationships between data directly, without mapping to relational rows and columns, and this makes them suitable for applications dealing with very complex data.\|Wikipedia\|[[w:Object_database#Comparison_with_RDBMSs\|functional difference between object and relational databases]]}}

	''' Lists of object databases '''		''' Lists of object databases '''
	* [[w:Object_database#Timeline\|Wikipedia's list of object databases by publication date.]]		* [[w:Object_database#Timeline\|Wikipedia's list of object databases by publication date.]]