equal
deleted
inserted
replaced
20 </p> |
20 </p> |
21 |
21 |
22 <p> |
22 <p> |
23 <strong>How can I help you?</strong> |
23 <strong>How can I help you?</strong> |
24 <br/> |
24 <br/> |
25 ... |
25 <ul> |
|
26 <li>Suggest more examples how <m:name/> can be used; especially how YOU would like to use it.</li> |
|
27 <li>We are looking for illustrations that would supplement our documentation and website.</li> |
|
28 <li> |
|
29 As an author of a program that generates or consumes some data, you could add relational input and output to your program. |
|
30 But please mention that we do not have v1.0 yet, so these features should be marked as experimental. |
|
31 The API might/will change. |
|
32 Other (and maybe better for now) option is to add input/output of values separated by null byte (<code>\0</code>). |
|
33 This "API" will be supported for sure and data are simply the attribute values. There are no record separators (we know the number of attributes, so they are not needed). |
|
34 Disadvantage of this approach is that the stream can contain only a single relation; and that the metadata are not embedded in the stream and must be passed separately. |
|
35 </li> |
|
36 <li>Review our source code and suggest improvements and fixes. Constructive criticism is always welcome. This is one of reasons why we publish our programs as free software.</li> |
|
37 <li>Native speakers could suggest improvements and corrections of our English texts.</li> |
|
38 </ul> |
26 </p> |
39 </p> |
27 |
40 |
28 <p> |
41 <p> |
29 <strong>Why do you speak about <em>relations</em> instead of <em>tables</em>?</strong> |
42 <strong>Why do you speak about <em>relations</em> instead of <em>tables</em>?</strong> |
30 <br/> |
43 <br/> |