Updating tables with foreign key constraints akatsuki dating sim online
More details: In HANA’s implementation of Foreign Keys, the possible referential actions pretty much follows the SQL Standard definition, with the exception of the “NO ACTION” action.Sources: These referential actions define how the constraint is going to act upon UPDATE/DELETE statements.Since it has the same name in both tables, I didn’t have to specify the referenced column name.Also, since I didn’t define any specific referential action, it assumes the default values (RESTRICT for both updates and deletes).Next, I altered the referential action of the FK to “CASCADE”, in order to evaluate its behvaior.
One of the functionalities in HANA SPS5 that makes it possible is exactly the enablement of Foreign Keys.What you can do is go to “Export SQL” in order to get the SQL statement that originated the table.In above’s case, this is what it looks like: CREATE COLUMN TABLE "TEST"."ORDER" ("ORDID" INTEGER CS_INT, "CUSTID" INTEGER CS_INT, "ORDDATE" DAYDATE CS_DAYDATE, "NETVAL" DECIMAL(23, 2) CS_FIXED, PRIMARY KEY ("ORDID")) ; CREATE BTREE INDEX "_SYS_CONSTRAINT_810121_#0_#F0" ON "TEST"."ORDER" ("CUSTID" ASC) Which leads to the assumption that FKs in HANA are nothing more than a particular case of BTREE indexes.One can observe that the type of the Delete Rule has changed by checking the “DELETE_RULE” column in the “REFERENTIAL_CONSTRAINTS” table. First, for the forbidden INSERT, the error message was the same.For the DELETE, however, since the new Delete Rule is “CASCADE”, we get a different behavior.