New answers tagged

0

A referential integrity constraint must reference a (unique) key of the parent table. Neither tbl.id_p nor tbl.id_c are declared as unique, so they can't be referenced by an RI constraint.


0

I believe the reason to why you get the error message is because in the first way of creating the table, you are referencing each column by itself. Which means there will need to be two Keys in the existing table for this CREATE statement to work. However the existing table only has one Key for both columns together (id_p, id_c). So since in the existing ...


2

There is a security consequence to setting SQL92_SECURITY to false. From https://www.stigviewer.com/stig/oracle_database_12c/2020-04-01/finding/V-61429 The configuration option SQL92_SECURITY specifies whether table-level SELECT privileges are required to execute an update or delete that references table column values. If this option is disabled (set to ...


2

Other than the obvious solution (grant select on data.xtest to app;), you can revert to the old behavior by setting SQL92_SECURITY to FALSE. In 11.2, its default value was FALSE, but in 19c, its default value is TRUE. alter system set sql92_security=false scope=spfile; Then restart the database, as this parameter can not be changed online. Demo: create ...


0

I guess that the permission in one file is wrong. Try do this: sudo chmod -x /usr/lib/systemd/system/mssql-server.service


0

Type conversion in expression (CONVERT(nvarchar(23),[soh].[SalesOrderID],0)) may affect "CardinalityEstimate" in query plan choice Since you are not aware about this warning message.It is important to point other example where this warning message MATTER. When there is data type mismatch between 2 Join condition then also you get this error. In ...


Top 50 recent answers are included