Eleven quick tips for properly handling tabular data. [PDF]
Hertz MI, McNeill AS.
europepmc +1 more source
(H-DIR)<sup>2</sup>: A Scalable Entropy-Based Framework for Anomaly Detection and Cybersecurity in Cloud IoT Data Centers. [PDF]
Tosi D, Pazzi R.
europepmc +1 more source
Causes and effects of fitness landscapes in system test generation: a replication study. [PDF]
Sahin O, Zhang M, Arcuri A.
europepmc +1 more source
Using the Avocado as an Evening Snack to Investigate Whole Food Matrix and Macronutrient Composition on Morning Metabolic Indices in Adults With Prediabetes. [PDF]
Preiss C +3 more
europepmc +1 more source
Continuous multimodal data supply chain and expandable clinical decision support for oncology. [PDF]
Chang JS +6 more
europepmc +1 more source
A python workflow definition for computational materials design.
Janssen J +10 more
europepmc +1 more source
CohortSymmetry: An R package to perform sequence symmetry analysis using the OMOP common data model
Chen X +18 more
europepmc +1 more source
In various writings over the past 20 years, such as [3], Date has pointed out that SQL produces incorrect answers to some queries where a null value is included in a table. In a recent article in the ACM SIGMOD Record, [8], Rubinson states that "Date misinterprets the meaning of his example query" and "SQL returns the correct answer to the query posed".
John Grant
openaire +2 more sources
Nulls, three-valued logic, and ambiguity in SQL
Date's popular critique of SQL's three-valued logic [4, 3] purports to demonstrate that SQL queries can produce erroneous results when nulls are present in the database. I argue that this critique is flawed in that Date misinterprets the meaning of his example query.
Claude Rubinson
openaire +2 more sources

