faq: relation vs. table
--- a/relpipe-data/faq.xml Fri Nov 30 17:53:43 2018 +0100
+++ b/relpipe-data/faq.xml Fri Nov 30 18:06:50 2018 +0100
@@ -26,7 +26,7 @@
</p>
<p>
- <strong>Why you speak about <em>relations</em> instead of <em>tables</em>?</strong>
+ <strong>Why do you speak about <em>relations</em> instead of <em>tables</em>?</strong>
<br/>
It might be uncommon terminology for someone, but <em>relations</em> and <em>attributes</em> symbolizes
that we focus on substance of the data. Pure data are conveyed through the pipelines
@@ -35,6 +35,13 @@
And tables (consisting of rows and columns) are only one of many possible options.
</p>
+ <m:tabulka>
+ Relational SQL alternative terms
+ relation table
+ attribute column field
+ record row tuple
+ </m:tabulka>
+
<!--
<p>
<strong>?</strong>
@@ -66,7 +73,7 @@
<strong>Why C++?</strong>
<br/>
Firstly, <m:name/> are a specification of a data format and as such are not bound to any programming language.
- This specification is totally language- and plafform- independent.
+ This specification is totally language- and platform- independent.
</p>
<p>
The ideal/perfect language does not exist and our implementations will be written in various languages.