Talk:Table creation: Difference between revisions
Content added Content deleted
(A DB but not necessarily SQL.) |
(new section →Turning this task into something useful) |
||
| Line 16: | Line 16: | ||
Changed the task too draft status as it is not clear that this task is about SQL table creation from its description. --[[User:Paddy3118|Paddy3118]] 05:19, 6 December 2010 (UTC) |
Changed the task too draft status as it is not clear that this task is about SQL table creation from its description. --[[User:Paddy3118|Paddy3118]] 05:19, 6 December 2010 (UTC) |
||
: I meant to respond to this months ago...See my comment above. --[[User:Short Circuit|Michael Mol]] 19:22, 20 June 2011 (UTC) |
: I meant to respond to this months ago...See my comment above. --[[User:Short Circuit|Michael Mol]] 19:22, 20 June 2011 (UTC) |
||
==Turning this task into something useful== |
|||
As others have pointed out, a "[Database] Table creation" task is redundant with [[Table_creation/Postal_addresses]] which is more practical, less fuzzily defined, and therefore a better task. |
|||
Based on the current task description and the original task author's own solution (PostgreSQL), it appears the point of this task here was to showcase the different data types supported by database languages, in a similar fashion to how tasks like [[Conditional_structures]] showcases language features of general-purpose programming languages. |
|||
In this spirit, I propose to: |
|||
* Rename the task to <b style="color:red">Database/Data types</b>. |
|||
* Either restrict the task to database languages, or make it a dual-purpose task: |
|||
** Database languages get to show what data types they support. |
|||
** General purpose languages get to show how their native data types map to the data types of a common database solution (e.g. SQlite). |
|||
<br>(See also my comment in [[Talk:Table_creation/Postal_addresses]].) |
|||
<br>--[[User:Smls|Smls]] ([[User talk:Smls|talk]]) 13:09, 31 July 2016 (UTC) |
|||