You need an index on the referencing table on ice_product_manuals (product_id).
See: dbfiddle-1
The composite index you have cannot be used for the FK constraint
for a peculiar reason. Normally, two (or more) column indexes can be used for FK constraints if the constraint is on the first column(s...
@PaulWhite yeah. I thought hashes would be involved from the first reading - and they were - but the details were interesting. It was not exactly what I expected.
> Msg 12135, Level 16, State 1 The Metadata needed for Optimized Locking is not populated yet. Please retry the operation. Msg 5069, Level 16, State 1 ALTER DATABASE statement failed.
> MySQL parses but ignores “inline REFERENCES specifications” (as defined in the SQL standard) where the references are defined as part of the column specification. MySQL accepts REFERENCES clauses only when specified as part of a separate FOREIGN KEY specification.
Eh it's probably another spaces vs tabs debate. But I learned Java before I got into C#. After I got into C# I remember when Java 8? (maybe 7?) dropped, and 7 of the 10 highlighted features were already in C# for multiple years at that point.
I never felt a need to go back to Java since. But obviously it's still has it's fair use, and community backing, even in mobile dev these days.
So I'm just dropping my opinion. Take it with a grain of salt.
@J.D. No that would be more of a SQL Server vs Postgres comparison: almost peers but one always seems to be ahead. This is more of a QBasic vs VB comparison: it's just a toy DB, there is no way anyone should be using it for serious work.
> * Scalar UDF returns results in different date and time formats when the Scalar UDF Inlining feature is enabled (added in SQL Server 2022 CU3 and SQL Server 2019 CU20)
In contrast, PostgreSQL actually seems like a pretty solid open source database system. And I don't particularly like to give complements to open source software lol.