Viewing 15 posts - 1 through 15 (of 193 total)
And that raises another of the basic tenets of data design - we should hold only that which is required and that which we do hold should be correct -...
March 11, 2020 at 2:27 pm
I'd suggest it would probably be better to store genetic phenotype rather than birth sex for medical purposes i.e. XX, XY which would correspond to birth sexes of female and...
March 11, 2020 at 8:59 am
This should not be a problem at the database tier in your tiered architecture. Do this in the input, before it even gets near the tables. You'll find ETL...
November 4, 2019 at 1:03 pm
Instead, check what will be...
March 1, 2019 at 10:41 am
March 1, 2019 at 9:54 am
February 28, 2019 at 2:42 am
December 17, 2018 at 10:21 am
I'd argue the version starting with the + is the "correct" format - that should be valid for calling from anywhere in the world. By convention the international access code...
November 2, 2018 at 5:14 am
Yes your right the GPExpess is on the RHS so as Jeff pointed out that would effectively turn it into an INNER JOIN.
That's what I get for not trying...
October 10, 2018 at 8:46 am
I tend to prefer keeping join criteria separate from filtering criteria so would generally go with a third option
LEFT OUTER JOIN Company.schema.GeneralParameter
October 10, 2018 at 8:06 am
September 28, 2018 at 7:23 am
An excellent point there Chris. I would want this set on any development machine but probably not on production machines. This is the same issue as we get in choosing...
September 28, 2018 at 2:49 am
August 30, 2018 at 10:45 am
Viewing 15 posts - 1 through 15 (of 193 total)