Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I think validation is incredibly important, but not necessarily in your situation. Which isn't to say that your situation is trivial, I just have my own date-oriented nits to pick.</p> <p>Specifically, my concerns are always in keeping things in logical order. If someone says they were born in 1802, that's fine (sorta), I just want their date of graduation to be greater than their date of birth. But you run into itchy little problems when it comes to time (as in hours and minutes), for instance, if a user chooses 8:30 as the start time and then chooses 9:15 as the end time, but then realizes that the end time was 8:45. They decide to change the 9 to an 8 with the intention of changing the minutes to :45. But my validation script is too busy saying "Hey Wait! 8:15 is before 8:30, nice try!" but I can't risk letting them leave it wrong, etc etc.</p> <p>For your situation specifically, I would lean toward what is ethical right. Because as it's been pointed out, someone could be entering a family history (with DOBs in the 1600's) or future purchases (with dates after today), so there is no realistic limit on dates in general. But there are limits to your scenario, ie:</p> <p>If Age is less than legal working age (16 in most parts of the US), don't even offer anything higher than that year as an option (if you are using drop down). </p> <p>If Age is beyond reasonable working age (which can be a sensitive subject) offer the highest value based on retirement age and simply add a ">" in front of that year. If someone is 75 and applying for an admin-level job, they will be more pleased that you made things simple rather than offended that you didn't have their year of birth listed. If anything, they will be impressed (I think) that you went this route instead of nothing at all, implying they shouldn't waste their time.</p> <p>In the end you have a simple drop down very easy to script (example in PHP):</p> <pre><code>$currentYear = date('Y'); echo "&lt;select name=\"YearOfBirth\"&gt;"; for($i = 16; $i &lt;= 64; $i++) { $optionYear = $currentYear - $i; echo "&lt;option value=\"$optionYear\"&gt;$optionYear&lt;/option&gt;"; } $greaterYear = $currentYear - 65; echo "&lt;option value=\"&amp;gt;$greaterYear\"&gt;&amp;gt;$greaterYear&lt;/option&gt;"; echo "&lt;/select&gt;"; </code></pre>
    singulars
    1. This table or related slice is empty.
    1. PO"Date of birth" validation: How far/much would you go?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USX-Cubed
    1. USAnthony
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTDownMod
    1. CO@Anthony: Well worded. Appreciate your insights from a fresh perspective.
      singulars
      1. PO
      1. USo.k.w
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload