You're missing the fundamental concept of a tiered architecture. Display formatting is done in a separate layer from the database. Yes, I know in the old days with COBOL and Fortran,...

There's a folk saying in the standards world that "the committee never met a feature he didn't like." And that's very true in the case of the joints in SQL....

>> This is not a design error. It does not violate the normal forms. <<

Normal forms are not the only kind of design error. ISO 11179 and the Metadata Committee...

>> ... joining hundreds of millions or billions of rows, dealing with big Cartesian products or when involving things like column store indexes. I've experienced it myself extracting data from...

>> I'd say ZERO chance that the professor id is some type of tax number. The security implications of that alone would prevent it. For many, their tax number would...

>> I agree that you should only store attributes as numeric types if you plan on doing math on them, .. <<

I agree and would add a caveat. Make sure...

>> The professorID is likely both the natural ID for the professor and the identity of the row. <<

We used to call people who used the identity table property as...

What are you trying to do? Why do you like screwed up presentation formats for your data? The whole idea of client/server architecture from the 1970s is that data is...

I disagree with this model. A table should represent a set of entities. What you are calling the generic type should be an attribute. But I would assume that a...

The identifiers for an entity are always on a nominal scale. You don't do any math with them, they don't represent a category, a magnitude or anything else. Here's a...

>>I have two tables: tblProfessors with professor_id as the primary key and tblStudents with StudentID as the primary key. <<

The use of the prefixed "TBL_" is a design error so...

We never intended for SQL to be used for text management. You ought to be using the proper tool to store this data. As part Lane put it in one...

We actually found that code is weirder than text. Text is pretty much read in a very straight left-to-right, top to bottom pattern of eye movements. Furthermore, proportional-spaced typefaces with...

Thanks to World War II, and modern newspapers, we have a lot of research on making typography readable. The University of Maryland also did studies on making code readable many...

CREATE TABLE Passaggi

(foobar_code VARCHAR(6) NOT NULL,

passagggio_timestamp DATETIME2(7) DEFAULT CURRENT TIMESTAMP NOT NULL,

PRIMARY KEY(foobar_code, passagggio_timestamp),

servizio_id SMALLINT NOT NULL);

>> I want to insert the record [sic: rows are not records] or do...