106:
the ORDER table (e.g., CUSTOMERID), which references the primary key of CUSTOMER (e.g. ID). Because the primary key of a table must be unique, and because CUSTOMERID only contains values from that primary key field, we may assume that, when it has a value, CUSTOMERID will identify the particular customer which placed the order. However, this can no longer be assumed if the ORDER table is not kept up to date when rows of the CUSTOMER table are deleted or the ID column altered, and working with these tables may become more difficult. Many real world databases work around this problem by 'inactivating' rather than physically deleting master table foreign keys, or by complex update programs that modify all references to a foreign key when a change is needed.
579:: your changes to a row may not be able to fully cascade because the row is referenced by data your transaction cannot "see", and therefore cannot cascade onto. An example: while your transaction is attempting to renumber a customer account, a simultaneous transaction is attempting to create a new invoice for that same customer; while a CASCADE rule may fix all the invoice rows your transaction can see to keep them consistent with the renumbered customer row, it won't reach into another transaction to fix the data there; because the database cannot guarantee consistent data when the two transactions commit, one of them will be forced to roll back (often on a first-come-first-served basis.)
1807:
1817:
1827:
572:(i.e. triggers with system-generated names, often hidden.) As such, they are subject to the same limitations as user-defined triggers, and their order of execution relative to other triggers may need to be considered; in some cases it may become necessary to replace the referential action with its equivalent user-defined trigger to ensure proper execution order, or to work around mutating-table limitations.
697:
invoice record has an attribute containing the supplier number for that invoice. Then, the 'supplier number' is the primary key in the
Supplier table. The foreign key in the Invoice table points to that primary key. The relational schema is the following. Primary keys are marked in bold, and foreign keys are marked in italics.
85:
The table containing the foreign key is called the child table, and the table containing the candidate key is called the referenced or parent table. In database relational modeling and implementation, a candidate key is a set of zero or more attributes, the values of which are guaranteed to be unique
541:
In other words, when an UPDATE or DELETE statement is executed on the referenced table using the referential action NO ACTION, the DBMS verifies at the end of the statement execution that none of the referential relationships are violated. This is different from RESTRICT, which assumes at the outset
62:
a candidate key. For example, a table called TEAM may have an attribute, MEMBER_NAME, which is a foreign key referencing a candidate key, PERSON_NAME, in the PERSON table. Since MEMBER_NAME is a foreign key, any value existing as the name of a member in TEAM must also exist as a person's name in the
504:
To understand RESTRICT (and CASCADE) better, it may be helpful to notice the following difference, which might not be immediately clear. The referential action CASCADE modifies the "behavior" of the (child) table itself where the word CASCADE is used. For example, ON DELETE CASCADE effectively says
696:
As a first example to illustrate foreign keys, suppose an accounts database has a table with invoices and each invoice is associated with a particular supplier. Supplier details (such as name and address) are kept in a separate table; each supplier is given a 'supplier number' to identify it. Each
105:
For example, consider a database with two tables: a CUSTOMER table that includes all customer data and an ORDER table that includes all customer orders. Suppose the business requires that each order must refer to a single customer. To reflect this in the database, a foreign key column is added to
113:. One important part of database design is making sure that relationships between real-world entities are reflected in the database by references, using foreign keys to refer from one table to another. Another important part of database design is
529:
NO ACTION and RESTRICT are very much alike. The main difference between NO ACTION and RESTRICT is that with NO ACTION the referential integrity check is done after trying to alter the table. RESTRICT does the check before trying to execute the
489:
Whenever rows in the parent (referenced) table are deleted (or updated), the respective rows of the child (referencing) table with a matching foreign key column will be deleted (or updated) as well. This is called a cascade delete (or update).
513:
the child table, although the word RESTRICT appears in the child table and not in the master table! So, ON DELETE RESTRICT effectively says: "When someone tries to delete the row from the other table (master table), prevent deletion
89:
Since the purpose of the foreign key is to identify a particular row of referenced table, it is generally required that the foreign key is equal to the candidate key in some row of the primary table, or else have no value (the
445:
enforces referential constraints, it must ensure data integrity if rows in a referenced table are to be deleted (or updated). If dependent rows in referencing tables still exist, those references have to be considered.
546:
or the semantics of the statement itself may yield an end state in which no foreign key relationships are violated by the time the constraint is finally checked, thus allowing the statement to complete successfully.
559:
for SET NULL or SET DEFAULT is the same for both ON DELETE or ON UPDATE: the value of the affected referencing attributes is changed to NULL for SET NULL, and to the specified default value for SET DEFAULT.
141:
A foreign key is defined as an attribute or set of attributes in a relation whose values match a primary key in another relation. The syntax to add such a constraint to an existing table is defined in
120:
Multiple rows in the referencing (or child) table may refer to the same row in the referenced (or parent) table. In this case, the relationship between the two tables is called a
86:
for each tuple (row) in a relation. The value or combination of values of candidate key attributes for any tuple cannot be duplicated for any other tuple in that relation.
131:
as a self-referencing or recursive foreign key. In database management systems, this is often accomplished by linking a first and second reference to the same table.
127:
In addition, the child and parent table may, in fact, be the same table, i.e. the foreign key refers back to the same table. Such a foreign key is known in
1417:
1400:
538:
statement. Both referential actions act the same if the referential integrity check fails: the UPDATE or DELETE statement will result in an error.
134:
A table may have multiple foreign keys, and each foreign key can have a different parent table. Each foreign key is enforced independently by the
149:
clause implies that the foreign key shall reference the primary key of the referenced table. Likewise, foreign keys can be defined as part of the
1412:
498:
A value cannot be updated or deleted when a row exists in a referencing or child table that references the value in the referenced table.
416:: the name of the table or view that has the primary key to which the foreign key applies. The primary key must already be defined.
426:: the name of the columns that make up the foreign key. The foreign key must have at least one column and at most eight columns.
1301:
1094:
1058:
51:, R, must also exist in some other (not necessarily distinct) relation, S; furthermore that those attributes must also be a
1851:
1810:
1483:
1372:
1119:
1268:
1189:
1144:
1340:
98:
between the two tables. Because violations of these constraints can be the source of many database problems, most
1830:
1536:
1787:
1434:
1726:
501:
Similarly, a row cannot be deleted as long as there is a reference to it from a referencing or child table.
576:
102:
provide mechanisms to ensure that every non-null foreign key corresponds to a row of the referenced table.
1721:
1335:
1752:
1471:
277:
If the foreign key is a single column only, the column can be marked as such using the following syntax:
121:
99:
1330:
1675:
1665:
1441:
442:
1762:
1495:
1293:
1160:
716:
117:, in which tables are broken apart and foreign keys make it possible for them to be reconstructed.
1711:
1365:
1325:
1856:
1792:
1747:
1424:
1086:
436:
114:
1214:
1767:
1521:
1286:
95:
1345:
1206:
1078:
138:. Therefore, cascading relationships between tables can be established using foreign keys.
1820:
1757:
1639:
1609:
1478:
1429:
40:
24:
8:
1777:
1670:
1655:
1582:
1407:
509:". However, the referential action RESTRICT modifies the "behavior" of the master table,
48:
36:
1861:
1772:
1716:
1685:
1634:
1526:
1466:
1358:
1592:
1446:
1297:
1264:
1241:
1218:
1207:
1185:
1140:
1115:
1090:
1079:
1054:
505:"When the referenced row is deleted from the other table (master table), then delete
1782:
1629:
1619:
1587:
569:
543:
372:
28:
1320:
73:
The referenced attribute must be a part of primary key of the referenced relation.
1690:
1660:
1614:
1395:
518:(and of course, also don't delete from me, but that's not the main point here)."
135:
110:
1742:
1680:
1624:
1597:
1490:
1451:
1029:
1350:
1845:
1561:
1546:
1014:
52:
410:: the name of the table or view that contains the foreign key to be defined.
1866:
1019:
535:
531:
1531:
32:
76:
Data type and size of referenced and referencing attribute must be same.
1695:
1604:
1566:
1541:
1245:
1222:
91:
63:
PERSON table; in other words, every member of a TEAM is also a PERSON.
542:
that the operation will violate the constraint. Using NO ACTION, the
1556:
1511:
1381:
1024:
447:
142:
128:
1461:
1053:. Independence KY: South-Western/Cengage Learning. p. 65.
35:
of another table, linking these two tables. In the context of
1456:
521:
RESTRICT is not supported by
Microsoft SQL 2012 and earlier.
44:
1516:
556:
58:
In other words, a foreign key is a set of attributes that
568:
Referential actions are generally implemented as implied
1051:
Database
Systems: Design, Implementation, and Management
124:
between the referencing table and the referenced table.
1346:Microsoft SQL 2012 table_constraint (Transact-SQL)
1285:
1182:MySQL Administrator's Guide and Language Reference
70:The reference relation should already be created.
1843:
145:as shown below. Omitting the column list in the
47:consisting of the foreign key attributes in one
1380:
1366:
1283:
1139:. John Wiley & Sons. pp. 119–122.
454:that shall take place in such occurrences:
1373:
1359:
575:Another important limitation appears with
478:
1072:
1070:
1179:
550:
1258:
1235:
1134:
1076:
1048:
109:Foreign keys play an essential role in
1844:
1263:. John Wiley & Sons. p. 156.
1204:
1067:
430:
1354:
1161:"Database Basics — Foreign Keys"
1109:
555:In general, the action taken by the
1826:
1288:Database Systems: The Complete Book
1209:Oracle SQL: Jumpstart with Examples
371:Foreign keys can be defined with a
13:
14:
1878:
1314:
39:, a foreign key is subject to an
1825:
1815:
1806:
1805:
1081:Fundamentals of Database Systems
96:referential integrity constraint
94:value.). This rule is called a
1816:
1341:SQLite support for Foreign Keys
1277:
1184:. Sams Publishing. p. 40.
1114:. Addison-Wesley. p. 206.
1284:Garcia-Molina, Hector (2009).
1252:
1229:
1198:
1173:
1153:
1128:
1103:
1042:
468:
1:
1035:
473:
463:
524:
458:
7:
1852:Database management systems
1382:Database management systems
1112:A guide to the SQL standard
1085:. Addison-Wesley. pp.
1008:
704:, Name, Address) Invoice (
563:
493:
100:database management systems
66:Important points to note:-
16:Concept in database systems
10:
1883:
1788:Object–relational database
1292:. Prentice Hall. pp.
691:
484:
443:database management system
434:
80:
1801:
1763:Federated database system
1735:
1704:
1648:
1575:
1504:
1496:Blockchain-based database
1388:
719:statement is as follows.
1336:FirebirdSQL primary Keys
1259:Sheldon, Robert (2005).
1135:Sheldon, Robert (2005).
1049:Coronel, Carlos (2010).
721:
717:Data Definition Language
581:
377:
279:
155:
122:one to many relationship
1326:PostgreSQL Foreign Keys
1236:Mullins, Craig (2012).
1077:Elmasri, Ramez (2011).
1793:Transaction processing
1748:Database normalization
1691:Query rewriting system
1205:Powell, Gavin (2004).
450:specifies 5 different
437:Propagation constraint
115:database normalization
1768:Referential integrity
1238:DB2 developer's guide
577:transaction isolation
551:SET NULL, SET DEFAULT
516:from that other table
1758:Distributed database
1213:. Elsevier. p.
1110:Date, C. J. (1996).
43:constraint that the
41:inclusion dependency
37:relational databases
1778:Relational calculus
1656:Concurrency control
1321:SQL-99 Foreign Keys
452:referential actions
431:Referential actions
31:that refers to the
1773:Relational algebra
1717:Query optimization
1522:Armstrong's axioms
1331:MySQL Foreign Keys
715:The corresponding
1839:
1838:
1447:Wide-column store
1442:Document-oriented
1303:978-0-13-187325-4
1180:MySQL AB (2006).
1096:978-0-13-608620-8
1060:978-0-538-74884-1
1874:
1829:
1828:
1819:
1818:
1809:
1808:
1783:Relational model
1753:Database storage
1630:Stored procedure
1375:
1368:
1361:
1352:
1351:
1308:
1307:
1291:
1281:
1275:
1274:
1256:
1250:
1249:
1233:
1227:
1226:
1212:
1202:
1196:
1195:
1177:
1171:
1170:
1168:
1167:
1157:
1151:
1150:
1132:
1126:
1125:
1107:
1101:
1100:
1084:
1074:
1065:
1064:
1046:
1004:
1001:
998:
995:
992:
989:
986:
983:
980:
977:
974:
971:
968:
965:
962:
959:
956:
953:
950:
947:
944:
941:
938:
935:
932:
929:
926:
923:
920:
917:
914:
911:
908:
905:
902:
899:
896:
893:
890:
887:
884:
881:
878:
875:
872:
869:
866:
863:
860:
857:
854:
851:
848:
845:
842:
839:
836:
833:
830:
827:
824:
821:
818:
815:
812:
809:
806:
803:
800:
797:
794:
791:
788:
785:
782:
779:
776:
773:
770:
767:
764:
761:
758:
755:
752:
749:
746:
743:
740:
737:
734:
731:
728:
725:
687:
684:
681:
678:
675:
672:
669:
666:
663:
660:
657:
654:
651:
648:
645:
642:
639:
636:
633:
630:
627:
624:
621:
618:
615:
612:
609:
606:
603:
600:
597:
594:
591:
588:
585:
402:
399:
396:
393:
390:
387:
384:
381:
373:stored procedure
367:
364:
361:
358:
355:
352:
349:
346:
343:
340:
337:
334:
331:
328:
325:
322:
319:
316:
313:
310:
307:
304:
301:
298:
295:
292:
289:
286:
283:
273:
270:
267:
264:
261:
258:
255:
252:
249:
246:
243:
240:
237:
234:
231:
228:
225:
222:
219:
216:
213:
210:
207:
204:
201:
198:
195:
192:
189:
186:
183:
180:
177:
174:
171:
168:
165:
162:
159:
152:
148:
1882:
1881:
1877:
1876:
1875:
1873:
1872:
1871:
1842:
1841:
1840:
1835:
1797:
1743:Database models
1731:
1700:
1686:Query optimizer
1661:Data dictionary
1644:
1615:Transaction log
1571:
1527:Codd's 12 rules
1500:
1430:Column-oriented
1396:Object-oriented
1384:
1379:
1317:
1312:
1311:
1304:
1282:
1278:
1271:
1261:Beginning MySQL
1257:
1253:
1234:
1230:
1203:
1199:
1192:
1178:
1174:
1165:
1163:
1159:
1158:
1154:
1147:
1137:Beginning MySQL
1133:
1129:
1122:
1108:
1104:
1097:
1075:
1068:
1061:
1047:
1043:
1038:
1011:
1006:
1005:
1002:
999:
996:
993:
990:
987:
984:
981:
978:
975:
972:
969:
966:
963:
960:
957:
954:
951:
948:
945:
942:
939:
936:
933:
930:
927:
924:
921:
918:
915:
912:
909:
906:
903:
900:
897:
894:
891:
888:
885:
882:
879:
876:
873:
870:
867:
864:
861:
858:
855:
852:
849:
846:
843:
840:
837:
834:
831:
828:
825:
822:
819:
816:
813:
810:
807:
804:
801:
798:
795:
792:
789:
786:
783:
780:
777:
774:
771:
768:
765:
762:
759:
756:
753:
750:
747:
744:
741:
738:
735:
732:
729:
726:
723:
713:
694:
689:
688:
685:
682:
679:
676:
673:
670:
667:
664:
661:
658:
655:
652:
649:
646:
643:
640:
637:
634:
631:
628:
625:
622:
619:
616:
613:
610:
607:
604:
601:
598:
595:
592:
589:
586:
583:
566:
553:
527:
496:
487:
439:
433:
404:
403:
400:
397:
394:
391:
388:
385:
382:
379:
369:
368:
365:
362:
359:
356:
353:
350:
347:
344:
341:
338:
335:
332:
329:
326:
323:
320:
317:
314:
311:
308:
305:
302:
299:
296:
293:
290:
287:
284:
281:
275:
274:
271:
268:
265:
262:
259:
256:
253:
250:
247:
244:
241:
238:
235:
232:
229:
226:
223:
220:
217:
214:
211:
208:
205:
202:
199:
196:
193:
190:
187:
184:
181:
178:
175:
172:
169:
166:
163:
160:
157:
153:SQL statement.
150:
146:
136:database system
111:database design
83:
17:
12:
11:
5:
1880:
1870:
1869:
1864:
1859:
1854:
1837:
1836:
1834:
1833:
1823:
1813:
1802:
1799:
1798:
1796:
1795:
1790:
1785:
1780:
1775:
1770:
1765:
1760:
1755:
1750:
1745:
1739:
1737:
1736:Related topics
1733:
1732:
1730:
1729:
1724:
1719:
1714:
1712:Administration
1708:
1706:
1702:
1701:
1699:
1698:
1693:
1688:
1683:
1681:Query language
1678:
1673:
1668:
1663:
1658:
1652:
1650:
1646:
1645:
1643:
1642:
1637:
1632:
1627:
1622:
1617:
1612:
1607:
1602:
1601:
1600:
1595:
1590:
1579:
1577:
1573:
1572:
1570:
1569:
1564:
1559:
1554:
1549:
1544:
1539:
1534:
1529:
1524:
1519:
1514:
1508:
1506:
1502:
1501:
1499:
1498:
1493:
1488:
1487:
1486:
1476:
1475:
1474:
1464:
1459:
1454:
1449:
1444:
1439:
1438:
1437:
1427:
1422:
1421:
1420:
1415:
1405:
1404:
1403:
1392:
1390:
1386:
1385:
1378:
1377:
1370:
1363:
1355:
1349:
1348:
1343:
1338:
1333:
1328:
1323:
1316:
1315:External links
1313:
1310:
1309:
1302:
1276:
1269:
1251:
1228:
1197:
1190:
1172:
1152:
1145:
1127:
1121:978-0201964264
1120:
1102:
1095:
1066:
1059:
1040:
1039:
1037:
1034:
1033:
1032:
1030:Junction table
1027:
1022:
1017:
1010:
1007:
979:SupplierNumber
964:SupplierNumber
889:SupplierNumber
832:SupplierNumber
814:SupplierNumber
736:SupplierNumber
722:
710:SupplierNumber
702:SupplierNumber
699:
693:
690:
582:
565:
562:
552:
549:
526:
523:
495:
492:
486:
483:
482:
481:
476:
471:
466:
461:
435:Main article:
432:
429:
428:
427:
417:
411:
378:
280:
156:
82:
79:
78:
77:
74:
71:
61:
15:
9:
6:
4:
3:
2:
1879:
1868:
1865:
1863:
1860:
1858:
1857:Data modeling
1855:
1853:
1850:
1849:
1847:
1832:
1824:
1822:
1814:
1812:
1804:
1803:
1800:
1794:
1791:
1789:
1786:
1784:
1781:
1779:
1776:
1774:
1771:
1769:
1766:
1764:
1761:
1759:
1756:
1754:
1751:
1749:
1746:
1744:
1741:
1740:
1738:
1734:
1728:
1725:
1723:
1720:
1718:
1715:
1713:
1710:
1709:
1707:
1703:
1697:
1694:
1692:
1689:
1687:
1684:
1682:
1679:
1677:
1674:
1672:
1669:
1667:
1664:
1662:
1659:
1657:
1654:
1653:
1651:
1647:
1641:
1638:
1636:
1633:
1631:
1628:
1626:
1623:
1621:
1618:
1616:
1613:
1611:
1608:
1606:
1603:
1599:
1596:
1594:
1591:
1589:
1586:
1585:
1584:
1581:
1580:
1578:
1574:
1568:
1565:
1563:
1562:Surrogate key
1560:
1558:
1555:
1553:
1550:
1548:
1547:Candidate key
1545:
1543:
1540:
1538:
1535:
1533:
1530:
1528:
1525:
1523:
1520:
1518:
1515:
1513:
1510:
1509:
1507:
1503:
1497:
1494:
1492:
1489:
1485:
1482:
1481:
1480:
1477:
1473:
1470:
1469:
1468:
1465:
1463:
1460:
1458:
1455:
1453:
1450:
1448:
1445:
1443:
1440:
1436:
1433:
1432:
1431:
1428:
1426:
1423:
1419:
1416:
1414:
1411:
1410:
1409:
1406:
1402:
1399:
1398:
1397:
1394:
1393:
1391:
1387:
1383:
1376:
1371:
1369:
1364:
1362:
1357:
1356:
1353:
1347:
1344:
1342:
1339:
1337:
1334:
1332:
1329:
1327:
1324:
1322:
1319:
1318:
1305:
1299:
1295:
1290:
1289:
1280:
1272:
1270:0-7645-7950-9
1266:
1262:
1255:
1247:
1243:
1240:. IBM Press.
1239:
1232:
1224:
1220:
1216:
1211:
1210:
1201:
1193:
1191:0-672-32870-4
1187:
1183:
1176:
1162:
1156:
1148:
1146:0-7645-7950-9
1142:
1138:
1131:
1123:
1117:
1113:
1106:
1098:
1092:
1088:
1083:
1082:
1073:
1071:
1062:
1056:
1052:
1045:
1041:
1031:
1028:
1026:
1023:
1021:
1018:
1016:
1015:Candidate key
1013:
1012:
937:InvoiceNumber
928:inumber_value
919:InvoiceNumber
859:InvoiceNumber
720:
718:
711:
707:
706:InvoiceNumber
703:
698:
580:
578:
573:
571:
561:
558:
548:
545:
539:
537:
533:
522:
519:
517:
512:
508:
502:
499:
491:
480:
477:
475:
472:
470:
467:
465:
462:
460:
457:
456:
455:
453:
449:
444:
438:
425:
421:
418:
415:
412:
409:
406:
405:
380:sp_foreignkey
376:
374:
278:
154:
144:
139:
137:
132:
130:
125:
123:
118:
116:
112:
107:
103:
101:
97:
93:
87:
75:
72:
69:
68:
67:
64:
59:
56:
54:
53:candidate key
50:
46:
42:
38:
34:
30:
26:
22:
1551:
1287:
1279:
1260:
1254:
1237:
1231:
1208:
1200:
1181:
1175:
1164:. Retrieved
1155:
1136:
1130:
1111:
1105:
1080:
1050:
1044:
1020:Compound key
823:number_value
714:
709:
705:
701:
695:
574:
567:
554:
540:
528:
520:
515:
510:
507:also from me
506:
503:
500:
497:
488:
451:
441:Because the
440:
423:
419:
414:parent_table
413:
407:
389:parent_table
370:
345:parent_table
276:
245:parent_table
151:CREATE TABLE
140:
133:
126:
119:
108:
104:
88:
84:
65:
57:
23:is a set of
20:
18:
1831:WikiProject
1722:Replication
1610:Transaction
1552:Foreign key
1532:CAP theorem
1479:Multi-model
952:supplier_fk
802:supplier_pk
479:SET DEFAULT
408:child_table
383:child_table
375:statement.
288:child_table
164:child_table
33:primary key
21:foreign key
1846:Categories
1696:Query plan
1649:Components
1567:Unique key
1484:comparison
1418:comparison
1408:Relational
1401:comparison
1246:B007Y6K9TK
1223:B008IU3AHY
1166:2010-03-13
1036:References
970:REFERENCES
949:CONSTRAINT
925:CONSTRAINT
907:invoice_pk
904:CONSTRAINT
820:CONSTRAINT
799:CONSTRAINT
700:Supplier (
342:REFERENCES
242:REFERENCES
147:REFERENCES
60:references
25:attributes
1862:Databases
1705:Functions
1640:Partition
1467:In-memory
1425:Key–value
525:NO ACTION
469:NO ACTION
312:CHARACTER
188:CHARACTER
1811:Category
1727:Sharding
1583:Relation
1557:Superkey
1512:Database
1505:Concepts
1025:Superkey
1009:See also
1000:RESTRICT
973:Supplier
730:Supplier
708:, Text,
596:acct_num
570:triggers
564:Triggers
544:triggers
494:RESTRICT
474:SET NULL
464:RESTRICT
448:SQL:2003
143:SQL:2003
129:SQL:2003
49:relation
1821:Outline
1620:Trigger
1576:Objects
991:CASCADE
955:FOREIGN
910:PRIMARY
892:INTEGER
877:VARCHAR
862:INTEGER
853:Invoice
805:PRIMARY
778:VARCHAR
775:Address
754:VARCHAR
739:INTEGER
692:Example
644:account
632:ins_sum
629:TRIGGER
608:DECIMAL
590:account
485:CASCADE
459:CASCADE
363:CASCADE
339:INTEGER
330:INTEGER
315:VARYING
300:PRIMARY
297:INTEGER
269:CASCADE
221:FOREIGN
215:INTEGER
206:INTEGER
191:VARYING
176:PRIMARY
173:INTEGER
81:Summary
55:in S.
1635:Cursor
1593:column
1462:NewSQL
1300:
1267:
1244:
1221:
1188:
1143:
1118:
1093:
1057:
997:DELETE
988:UPDATE
847:CREATE
724:CREATE
683:amount
638:INSERT
635:BEFORE
626:CREATE
605:amount
584:CREATE
536:DELETE
532:UPDATE
360:DELETE
282:CREATE
266:DELETE
158:CREATE
45:tuples
1625:Index
1588:table
1491:Cloud
1457:NoSQL
1452:Graph
1389:Types
1296:–95.
1089:–74.
931:CHECK
850:TABLE
826:CHECK
727:TABLE
587:TABLE
285:TABLE
161:TABLE
29:table
27:in a
1676:ODBC
1666:JDBC
1605:View
1542:Null
1537:CRUD
1517:ACID
1472:list
1435:list
1413:list
1298:ISBN
1265:ISBN
1242:ASIN
1219:ASIN
1186:ISBN
1141:ISBN
1116:ISBN
1091:ISBN
1055:ISBN
940:>
898:NULL
883:4096
874:Text
868:NULL
835:>
793:NULL
769:NULL
751:Name
745:NULL
650:EACH
557:DBMS
424:col4
422:and
420:col3
401:col4
395:col3
351:col1
336:col4
327:col3
309:col2
294:col1
257:col2
251:col1
236:col4
230:col3
212:col4
203:col3
185:col2
170:col1
92:NULL
1867:SQL
1671:XQJ
1598:row
958:KEY
913:KEY
895:NOT
865:NOT
808:KEY
790:NOT
766:NOT
742:NOT
677:NEW
671:sum
662:sum
656:SET
653:ROW
647:FOR
623:));
599:INT
534:or
511:not
303:KEY
224:KEY
179:KEY
1848::
1294:93
1217:.
1215:11
1087:73
1069:^
994:ON
985:ON
946:),
922:),
886:),
817:),
784:50
760:20
712:)
641:ON
614:10
357:ON
324:),
321:20
263:ON
200:),
197:20
19:A
1374:e
1367:t
1360:v
1306:.
1273:.
1248:.
1225:.
1194:.
1169:.
1149:.
1124:.
1099:.
1063:.
1003:)
982:)
976:(
967:)
961:(
943:0
934:(
916:(
901:,
880:(
871:,
856:(
844:)
841:)
838:0
829:(
811:(
796:,
787:)
781:(
772:,
763:)
757:(
748:,
733:(
686:;
680:.
674:+
668:@
665:=
659:@
620:2
617:,
611:(
602:,
593:(
398:,
392:,
386:,
366:)
354:)
348:(
333:,
318:(
306:,
291:(
272:)
260:)
254:,
248:(
239:)
233:,
227:(
218:,
209:,
194:(
182:,
167:(
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.