bin/x64/System.Data.SQLite.Linq.xml
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 |
<?xml version="1.0"?>
<doc> <assembly> <name>System.Data.SQLite.Linq</name> </assembly> <members> <member name="T:System.Data.SQLite.Properties.Resources"> <summary> A strongly-typed resource class, for looking up localized strings, etc. </summary> </member> <member name="P:System.Data.SQLite.Properties.Resources.ResourceManager"> <summary> Returns the cached ResourceManager instance used by this class. </summary> </member> <member name="P:System.Data.SQLite.Properties.Resources.Culture"> <summary> Overrides the current thread's CurrentUICulture property for all resource lookups using this strongly typed resource class. </summary> </member> <member name="P:System.Data.SQLite.Properties.Resources.SQL_CONSTRAINTCOLUMNS"> <summary> Looks up a localized string similar to CREATE TEMP VIEW SCHEMACONSTRAINTCOLUMNS AS SELECT CONSTRAINT_CATALOG, NULL AS CONSTRAINT_SCHEMA, CONSTRAINT_NAME, TABLE_CATALOG, NULL AS TABLE_SCHEMA, TABLE_NAME, COLUMN_NAME FROM TEMP.SCHEMAINDEXCOLUMNS UNION SELECT CONSTRAINT_CATALOG, NULL, CONSTRAINT_NAME, TABLE_CATALOG, NULL, TABLE_NAME, FKEY_FROM_COLUMN FROM TEMP.SCHEMAFOREIGNKEYS;. </summary> </member> <member name="P:System.Data.SQLite.Properties.Resources.SQL_CONSTRAINTS"> <summary> Looks up a localized string similar to CREATE TEMP VIEW SCHEMACONSTRAINTS AS SELECT INDEX_CATALOG AS CONSTRAINT_CATALOG, NULL AS CONSTRAINT_SCHEMA, INDEX_NAME AS CONSTRAINT_NAME, TABLE_CATALOG, NULL AS TABLE_SCHEMA, TABLE_NAME, 'PRIMARY KEY' AS CONSTRAINT_TYPE, 0 AS IS_DEFERRABLE, 0 AS INITIALLY_DEFERRED, NULL AS CHECK_CLAUSE FROM TEMP.SCHEMAINDEXES WHERE PRIMARY_KEY = 1 UNION SELECT INDEX_CATALOG, NULL, INDEX_NAME, TABLE_CATALOG, NULL, TABLE_NAME, 'UNIQUE', 0, 0, NULL FROM TEMP.SCHEMAINDEXES WHERE PRIMARY_KEY = 0 AND [UNIQUE] = 1 UNION [rest of string was truncated]";. </summary> </member> <member name="T:System.Data.SQLite.DmlSqlGenerator"> <summary> Class generating SQL for a DML command tree. </summary> </member> <member name="M:System.Data.SQLite.DmlSqlGenerator.GenerateReturningSql(System.Text.StringBuilder,System.Data.Common.CommandTrees.DbModificationCommandTree,System.Data.SQLite.DmlSqlGenerator.ExpressionTranslator,System.Data.Common.CommandTrees.DbExpression)"> <summary> Generates SQL fragment returning server-generated values. Requires: translator knows about member values so that we can figure out how to construct the key predicate. <code> Sample SQL: select IdentityValue from dbo.MyTable where @@ROWCOUNT > 0 and IdentityValue = scope_identity() or select TimestamptValue from dbo.MyTable where @@ROWCOUNT > 0 and Id = 1 Note that we filter on rowcount to ensure no rows are returned if no rows were modified. </code> </summary> <param name="commandText">Builder containing command text</param> <param name="tree">Modification command tree</param> <param name="translator">Translator used to produce DML SQL statement for the tree</param> <param name="returning">Returning expression. If null, the method returns immediately without producing a SELECT statement.</param> </member> <member name="T:System.Data.SQLite.DmlSqlGenerator.ExpressionTranslator"> <summary> Lightweight expression translator for DML expression trees, which have constrained scope and support. </summary> </member> <member name="M:System.Data.SQLite.DmlSqlGenerator.ExpressionTranslator.#ctor(System.Text.StringBuilder,System.Data.Common.CommandTrees.DbModificationCommandTree,System.Boolean,System.String)"> <summary> Initialize a new expression translator populating the given string builder with command text. Command text builder and command tree must not be null. </summary> <param name="commandText">Command text with which to populate commands</param> <param name="commandTree">Command tree generating SQL</param> <param name="preserveMemberValues">Indicates whether the translator should preserve member values while compiling t-SQL (only needed for server generation)</param> <param name="kind"></param> </member> <member name="M:System.Data.SQLite.DmlSqlGenerator.ExpressionTranslator.RegisterMemberValue(System.Data.Common.CommandTrees.DbExpression,System.Data.Common.CommandTrees.DbExpression)"> <summary> Call this method to register a property value pair so the translator "remembers" the values for members of the row being modified. These values can then be used to form a predicate for server-generation (based on the key of the row) </summary> <param name="propertyExpression">DbExpression containing the column reference (property expression).</param> <param name="value">DbExpression containing the value of the column.</param> </member> <member name="T:System.Data.SQLite.ISqlFragment"> <summary> Represents the sql fragment for any node in the query tree. </summary> <remarks> The nodes in a query tree produce various kinds of sql <list type="bullet"> <item>A select statement.</item> <item>A reference to an extent. (symbol)</item> <item>A raw string.</item> </list> We have this interface to allow for a common return type for the methods in the expression visitor <see cref="T:System.Data.Common.CommandTrees.DbExpressionVisitor`1"/> At the end of translation, the sql fragments are converted into real strings. </remarks> </member> <member name="M:System.Data.SQLite.ISqlFragment.WriteSql(System.Data.SQLite.SqlWriter,System.Data.SQLite.SqlGenerator)"> <summary> Write the string represented by this fragment into the stream. </summary> <param name="writer">The stream that collects the strings.</param> <param name="sqlGenerator">Context information used for renaming. The global lists are used to generated new names without collisions.</param> </member> <member name="T:System.Data.SQLite.JoinSymbol"> <summary> A Join symbol is a special kind of Symbol. It has to carry additional information <list type="bullet"> <item>ColumnList for the list of columns in the select clause if this symbol represents a sql select statement. This is set by <see cref="M:System.Data.SQLite.SqlGenerator.AddDefaultColumns(System.Data.SQLite.SqlSelectStatement)"/>. </item> <item>ExtentList is the list of extents in the select clause.</item> <item>FlattenedExtentList - if the Join has multiple extents flattened at the top level, we need this information to ensure that extent aliases are renamed correctly in <see cref="M:System.Data.SQLite.SqlSelectStatement.WriteSql(System.Data.SQLite.SqlWriter,System.Data.SQLite.SqlGenerator)"/></item> <item>NameToExtent has all the extents in ExtentList as a dictionary. This is used by <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbPropertyExpression)"/> to flatten record accesses.</item> <item>IsNestedJoin - is used to determine whether a JoinSymbol is an ordinary join symbol, or one that has a corresponding SqlSelectStatement.</item> </list> All the lists are set exactly once, and then used for lookups/enumerated. </summary> </member> <member name="T:System.Data.SQLite.Symbol"> <summary> <see cref="T:System.Data.SQLite.SymbolTable"/> This class represents an extent/nested select statement, or a column. The important fields are Name, Type and NewName. NewName starts off the same as Name, and is then modified as necessary. The rest are used by special symbols. e.g. NeedsRenaming is used by columns to indicate that a new name must be picked for the column in the second phase of translation. IsUnnest is used by symbols for a collection expression used as a from clause. This allows <see cref="M:System.Data.SQLite.SqlGenerator.AddFromSymbol(System.Data.SQLite.SqlSelectStatement,System.String,System.Data.SQLite.Symbol,System.Boolean)"/> to add the column list after the alias. </summary> </member> <member name="M:System.Data.SQLite.Symbol.WriteSql(System.Data.SQLite.SqlWriter,System.Data.SQLite.SqlGenerator)"> <summary> Write this symbol out as a string for sql. This is just the new name of the symbol (which could be the same as the old name). We rename columns here if necessary. </summary> <param name="writer"></param> <param name="sqlGenerator"></param> </member> <member name="T:System.Data.SQLite.MetadataHelpers"> <summary> A set of static helpers for type metadata </summary> </member> <member name="F:System.Data.SQLite.MetadataHelpers.NullableFacetName"> <summary> Name of the Nullable Facet </summary> </member> <member name="M:System.Data.SQLite.MetadataHelpers.GetEdmType``1(System.Data.Metadata.Edm.TypeUsage)"> <summary> Cast the EdmType of the given type usage to the given TEdmType </summary> <typeparam name="TEdmType"></typeparam> <param name="typeUsage"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.GetElementTypeUsage(System.Data.Metadata.Edm.TypeUsage)"> <summary> Gets the TypeUsage of the elment if the given type is a collection type </summary> <param name="type"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.GetProperties(System.Data.Metadata.Edm.TypeUsage)"> <summary> Retrieves the properties of in the EdmType underlying the input type usage, if that EdmType is a structured type (EntityType, RowType). </summary> <param name="typeUsage"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.GetProperties(System.Data.Metadata.Edm.EdmType)"> <summary> Retrieves the properties of the given EdmType, if it is a structured type (EntityType, RowType). </summary> <param name="edmType"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.IsCollectionType(System.Data.Metadata.Edm.TypeUsage)"> <summary> Is the given type usage over a collection type </summary> <param name="typeUsage"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.IsCollectionType(System.Data.Metadata.Edm.EdmType)"> <summary> Is the given type a collection type </summary> <param name="type"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.IsPrimitiveType(System.Data.Metadata.Edm.TypeUsage)"> <summary> Is the given type usage over a primitive type </summary> <param name="type"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.IsPrimitiveType(System.Data.Metadata.Edm.EdmType)"> <summary> Is the given type a primitive type </summary> <param name="type"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.IsRowType(System.Data.Metadata.Edm.TypeUsage)"> <summary> Is the given type usage over a row type </summary> <param name="type"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.IsRowType(System.Data.Metadata.Edm.EdmType)"> <summary> Is the given type a row type </summary> <param name="type"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.TryGetPrimitiveTypeKind(System.Data.Metadata.Edm.TypeUsage,System.Data.Metadata.Edm.PrimitiveTypeKind@)"> <summary> Gets the type of the given type usage if it is a primitive type </summary> <param name="type"></param> <param name="typeKind"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.TryGetValueForMetadataProperty``1(System.Data.Metadata.Edm.MetadataItem,System.String)"> <summary> Gets the value for the metadata property with the given name </summary> <typeparam name="T"></typeparam> <param name="item"></param> <param name="propertyName"></param> <returns></returns> </member> <member name="F:System.Data.SQLite.MetadataHelpers.MaxLengthFacetName"> <summary> Name of the MaxLength Facet </summary> </member> <member name="F:System.Data.SQLite.MetadataHelpers.UnicodeFacetName"> <summary> Name of the Unicode Facet </summary> </member> <member name="F:System.Data.SQLite.MetadataHelpers.FixedLengthFacetName"> <summary> Name of the FixedLength Facet </summary> </member> <member name="F:System.Data.SQLite.MetadataHelpers.PreserveSecondsFacetName"> <summary> Name of the PreserveSeconds Facet </summary> </member> <member name="F:System.Data.SQLite.MetadataHelpers.PrecisionFacetName"> <summary> Name of the Precision Facet </summary> </member> <member name="F:System.Data.SQLite.MetadataHelpers.ScaleFacetName"> <summary> Name of the Scale Facet </summary> </member> <member name="F:System.Data.SQLite.MetadataHelpers.DefaultValueFacetName"> <summary> Name of the DefaultValue Facet </summary> </member> <member name="M:System.Data.SQLite.MetadataHelpers.GetFacetValueOrDefault``1(System.Data.Metadata.Edm.TypeUsage,System.String,``0)"> <summary> Get the value specified on the given type usage for the given facet name. If the faces does not have a value specifid or that value is null returns the default value for that facet. </summary> <typeparam name="T"></typeparam> <param name="type"></param> <param name="facetName"></param> <param name="defaultValue"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.MetadataHelpers.TryGetTypeFacetDescriptionByName(System.Data.Metadata.Edm.EdmType,System.String,System.Data.Metadata.Edm.FacetDescription@)"> <summary> Given a facet name and an EdmType, tries to get that facet's description. </summary> <param name="edmType"></param> <param name="facetName"></param> <param name="facetDescription"></param> <returns></returns> </member> <member name="T:System.Data.SQLite.SkipClause"> <summary> SkipClause represents the a SKIP expression in a SqlSelectStatement. It has a count property, which indicates how many rows should be skipped. </summary> </member> <member name="M:System.Data.SQLite.SkipClause.#ctor(System.Data.SQLite.ISqlFragment)"> <summary> Creates a SkipClause with the given skipCount. </summary> <param name="skipCount"></param> </member> <member name="M:System.Data.SQLite.SkipClause.#ctor(System.Int32)"> <summary> Creates a SkipClause with the given skipCount. </summary> <param name="skipCount"></param> </member> <member name="M:System.Data.SQLite.SkipClause.WriteSql(System.Data.SQLite.SqlWriter,System.Data.SQLite.SqlGenerator)"> <summary> Write out the SKIP part of sql select statement It basically writes OFFSET (X). </summary> <param name="writer"></param> <param name="sqlGenerator"></param> </member> <member name="P:System.Data.SQLite.SkipClause.SkipCount"> <summary> How many rows should be skipped. </summary> </member> <member name="T:System.Data.SQLite.SqlBuilder"> <summary> This class is like StringBuilder. While traversing the tree for the first time, we do not know all the strings that need to be appended e.g. things that need to be renamed, nested select statements etc. So, we use a builder that can collect all kinds of sql fragments. </summary> </member> <member name="M:System.Data.SQLite.SqlBuilder.Append(System.Object)"> <summary> Add an object to the list - we do not verify that it is a proper sql fragment since this is an internal method. </summary> <param name="s"></param> </member> <member name="M:System.Data.SQLite.SqlBuilder.AppendLine"> <summary> This is to pretty print the SQL. The writer <see cref="M:System.Data.SQLite.SqlWriter.Write(System.String)"/> needs to know about new lines so that it can add the right amount of indentation at the beginning of lines. </summary> </member> <member name="M:System.Data.SQLite.SqlBuilder.WriteSql(System.Data.SQLite.SqlWriter,System.Data.SQLite.SqlGenerator)"> <summary> We delegate the writing of the fragment to the appropriate type. </summary> <param name="writer"></param> <param name="sqlGenerator"></param> </member> <member name="P:System.Data.SQLite.SqlBuilder.IsEmpty"> <summary> Whether the builder is empty. This is used by the <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbProjectExpression)"/> to determine whether a sql statement can be reused. </summary> </member> <member name="T:System.Data.SQLite.SqlGenerator"> <summary> Translates the command object into a SQL string that can be executed on SQLite. </summary> <remarks> The translation is implemented as a visitor <see cref="T:System.Data.Common.CommandTrees.DbExpressionVisitor`1"/> over the query tree. It makes a single pass over the tree, collecting the sql fragments for the various nodes in the tree <see cref="T:System.Data.SQLite.ISqlFragment"/>. The major operations are <list type="bullet"> <item>Select statement minimization. Multiple nodes in the query tree that can be part of a single SQL select statement are merged. e.g. a Filter node that is the input of a Project node can typically share the same SQL statement.</item> <item>Alpha-renaming. As a result of the statement minimization above, there could be name collisions when using correlated subqueries <example> <code> Filter( b = Project( c.x c = Extent(foo) ) exists ( Filter( c = Extent(foo) b.x = c.x ) ) ) </code> The first Filter, Project and Extent will share the same SQL select statement. The alias for the Project i.e. b, will be replaced with c. If the alias c for the Filter within the exists clause is not renamed, we will get <c>c.x = c.x</c>, which is incorrect. Instead, the alias c within the second filter should be renamed to c1, to give <c>c.x = c1.x</c> i.e. b is renamed to c, and c is renamed to c1. </example> </item> <item>Join flattening. In the query tree, a list of join nodes is typically represented as a tree of Join nodes, each with 2 children. e.g. <example> <code> a = Join(InnerJoin b = Join(CrossJoin c = Extent(foo) d = Extent(foo) ) e = Extent(foo) on b.c.x = e.x ) </code> If translated directly, this will be translated to <code> FROM ( SELECT c.*, d.* FROM foo as c CROSS JOIN foo as d) as b INNER JOIN foo as e on b.x' = e.x </code> It would be better to translate this as <code> FROM foo as c CROSS JOIN foo as d INNER JOIN foo as e on c.x = e.x </code> This allows the optimizer to choose an appropriate join ordering for evaluation. </example> </item> <item>Select * and column renaming. In the example above, we noticed that in some cases we add <c>SELECT * FROM ...</c> to complete the SQL statement. i.e. there is no explicit PROJECT list. In this case, we enumerate all the columns available in the FROM clause This is particularly problematic in the case of Join trees, since the columns from the extents joined might have the same name - this is illegal. To solve this problem, we will have to rename columns if they are part of a SELECT * for a JOIN node - we do not need renaming in any other situation. <see cref="M:System.Data.SQLite.SqlGenerator.AddDefaultColumns(System.Data.SQLite.SqlSelectStatement)"/>. </item> </list> <para> Renaming issues. When rows or columns are renamed, we produce names that are unique globally with respect to the query. The names are derived from the original names, with an integer as a suffix. e.g. CustomerId will be renamed to CustomerId1, CustomerId2 etc. Since the names generated are globally unique, they will not conflict when the columns of a JOIN SELECT statement are joined with another JOIN. </para> <para> Record flattening. SQL server does not have the concept of records. However, a join statement produces records. We have to flatten the record accesses into a simple <c>alias.column</c> form. <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbPropertyExpression)"/> </para> <para> Building the SQL. There are 2 phases <list type="numbered"> <item>Traverse the tree, producing a sql builder <see cref="T:System.Data.SQLite.SqlBuilder"/></item> <item>Write the SqlBuilder into a string, renaming the aliases and columns as needed.</item> </list> In the first phase, we traverse the tree. We cannot generate the SQL string right away, since <list type="bullet"> <item>The WHERE clause has to be visited before the from clause.</item> <item>extent aliases and column aliases need to be renamed. To minimize renaming collisions, all the names used must be known, before any renaming choice is made.</item> </list> To defer the renaming choices, we use symbols <see cref="T:System.Data.SQLite.Symbol"/>. These are renamed in the second phase. Since visitor methods cannot transfer information to child nodes through parameters, we use some global stacks, <list type="bullet"> <item>A stack for the current SQL select statement. This is needed by <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbVariableReferenceExpression)"/> to create a list of free variables used by a select statement. This is needed for alias renaming. </item> <item>A stack for the join context. When visiting a <see cref="T:System.Data.Common.CommandTrees.DbScanExpression"/>, we need to know whether we are inside a join or not. If we are inside a join, we do not create a new SELECT statement.</item> </list> </para> <para> Global state. To enable renaming, we maintain <list type="bullet"> <item>The set of all extent aliases used.</item> <item>The set of all column aliases used.</item> </list> Finally, we have a symbol table to lookup variable references. All references to the same extent have the same symbol. </para> <para> Sql select statement sharing. Each of the relational operator nodes <list type="bullet"> <item>Project</item> <item>Filter</item> <item>GroupBy</item> <item>Sort/OrderBy</item> </list> can add its non-input (e.g. project, predicate, sort order etc.) to the SQL statement for the input, or create a new SQL statement. If it chooses to reuse the input's SQL statement, we play the following symbol table trick to accomplish renaming. The symbol table entry for the alias of the current node points to the symbol for the input in the input's SQL statement. <example> <code> Project(b.x b = Filter( c = Extent(foo) c.x = 5) ) </code> The Extent node creates a new SqlSelectStatement. This is added to the symbol table by the Filter as {c, Symbol(c)}. Thus, <c>c.x</c> is resolved to <c>Symbol(c).x</c>. Looking at the project node, we add {b, Symbol(c)} to the symbol table if the SQL statement is reused, and {b, Symbol(b)}, if there is no reuse. Thus, <c>b.x</c> is resolved to <c>Symbol(c).x</c> if there is reuse, and to <c>Symbol(b).x</c> if there is no reuse. </example> </para> </remarks> </member> <member name="F:System.Data.SQLite.SqlGenerator.selectStatementStack"> <summary> Every relational node has to pass its SELECT statement to its children This allows them (DbVariableReferenceExpression eventually) to update the list of outer extents (free variables) used by this select statement. </summary> </member> <member name="F:System.Data.SQLite.SqlGenerator.isParentAJoinStack"> <summary> Nested joins and extents need to know whether they should create a new Select statement, or reuse the parent's. This flag indicates whether the parent is a join or not. </summary> </member> <member name="F:System.Data.SQLite.SqlGenerator.isVarRefSingle"> <summary> VariableReferenceExpressions are allowed only as children of DbPropertyExpression or MethodExpression. The cheapest way to ensure this is to set the following property in DbVariableReferenceExpression and reset it in the allowed parent expressions. </summary> </member> <member name="M:System.Data.SQLite.SqlGenerator.InitializeBuiltInFunctionHandlers"> <summary> All special built-in functions and their handlers </summary> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.InitializeCanonicalFunctionHandlers"> <summary> All special non-aggregate canonical functions and their handlers </summary> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.InitializeDatepartKeywords"> <summary> Valid datepart values </summary> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.InitializeFunctionNameToOperatorDictionary"> <summary> Initializes the mapping from functions to T-SQL operators for all functions that translate to T-SQL operators </summary> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.#ctor(System.Data.SQLite.SQLiteProviderManifest)"> <summary> Basic constructor. </summary> </member> <member name="M:System.Data.SQLite.SqlGenerator.GenerateSql(System.Data.SQLite.SQLiteProviderManifest,System.Data.Common.CommandTrees.DbCommandTree,System.Collections.Generic.List{System.Data.Common.DbParameter}@,System.Data.CommandType@)"> <summary> General purpose static function that can be called from System.Data assembly </summary> <param name="manifest"></param> <param name="tree">command tree</param> <param name="parameters">Parameters to add to the command tree corresponding to constants in the command tree. Used only in ModificationCommandTrees.</param> <param name="commandType"></param> <returns>The string representing the SQL to be executed.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.GenerateSql(System.Data.Common.CommandTrees.DbQueryCommandTree)"> <summary> Translate a command tree to a SQL string. The input tree could be translated to either a SQL SELECT statement or a SELECT expression. This choice is made based on the return type of the expression CollectionType => select statement non collection type => select expression </summary> <param name="tree"></param> <returns>The string representing the SQL to be executed.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.GenerateFunctionSql(System.Data.Common.CommandTrees.DbFunctionCommandTree,System.Data.CommandType@)"> <summary> Translate a function command tree to a SQL string. </summary> </member> <member name="M:System.Data.SQLite.SqlGenerator.WriteSql(System.Data.SQLite.ISqlFragment)"> <summary> Convert the SQL fragments to a string. We have to setup the Stream for writing. </summary> <param name="sqlStatement"></param> <returns>A string representing the SQL to be executed.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbAndExpression)"> <summary> Translate(left) AND Translate(right) </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/>.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbApplyExpression)"> <summary> An apply is just like a join, so it shares the common join processing in <see cref="M:System.Data.SQLite.SqlGenerator.VisitJoinExpression(System.Collections.Generic.IList{System.Data.Common.CommandTrees.DbExpressionBinding},System.Data.Common.CommandTrees.DbExpressionKind,System.String,System.Data.Common.CommandTrees.DbExpression)"/> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/>.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbArithmeticExpression)"> <summary> For binary expressions, we delegate to <see cref="M:System.Data.SQLite.SqlGenerator.VisitBinaryExpression(System.String,System.Data.Common.CommandTrees.DbExpression,System.Data.Common.CommandTrees.DbExpression)"/>. We handle the other expressions directly. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbCaseExpression)"> <summary> If the ELSE clause is null, we do not write it out. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbCastExpression)"> <summary> </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbComparisonExpression)"> <summary> The parser generates Not(Equals(...)) for <>. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/>.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbConstantExpression)"> <summary> Constants will be send to the store as part of the generated TSQL, not as parameters </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/>. Strings are wrapped in single quotes and escaped. Numbers are written literally.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbDerefExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbDerefExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbDistinctExpression)"> <summary> The DISTINCT has to be added to the beginning of SqlSelectStatement.Select, but it might be too late for that. So, we use a flag on SqlSelectStatement instead, and add the "DISTINCT" in the second phase. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbElementExpression)"> <summary> An element expression returns a scalar - so it is translated to ( Select ... ) </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbExceptExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbUnionAllExpression)"/> </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbExpression)"> <summary> Only concrete expression types will be visited. </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbScanExpression)"> <summary> </summary> <param name="e"></param> <returns>If we are in a Join context, returns a <see cref="T:System.Data.SQLite.SqlBuilder"/> with the extent name, otherwise, a new <see cref="T:System.Data.SQLite.SqlSelectStatement"/> with the From field set.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.GetTargetTSql(System.Data.Metadata.Edm.EntitySetBase)"> <summary> Gets escaped TSql identifier describing this entity set. </summary> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"> <summary> The bodies of <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"/>, <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbGroupByExpression)"/>, <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbProjectExpression)"/>, <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbSortExpression)"/> are similar. Each does the following. <list type="number"> <item> Visit the input expression</item> <item> Determine if the input's SQL statement can be reused, or a new one must be created.</item> <item>Create a new symbol table scope</item> <item>Push the Sql statement onto a stack, so that children can update the free variable list.</item> <item>Visit the non-input expression.</item> <item>Cleanup</item> </list> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Lambda functions are not supported. The functions supported are: <list type="number"> <item>Canonical Functions - We recognize these by their dataspace, it is DataSpace.CSpace</item> <item>Store Functions - We recognize these by the BuiltInAttribute and not being Canonical</item> <item>User-defined Functions - All the rest except for Lambda functions</item> </list> We handle Canonical and Store functions the same way: If they are in the list of functions that need special handling, we invoke the appropriate handler, otherwise we translate them to FunctionName(arg1, arg2, ..., argn). We translate user-defined functions to NamespaceName.FunctionName(arg1, arg2, ..., argn). </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbEntityRefExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbEntityRefExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbRefKeyExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbRefKeyExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbGroupByExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"/> for general details. We modify both the GroupBy and the Select fields of the SqlSelectStatement. GroupBy gets just the keys without aliases, and Select gets the keys and the aggregates with aliases. Whenever there exists at least one aggregate with an argument that is not is not a simple <see cref="T:System.Data.Common.CommandTrees.DbPropertyExpression"/> over <see cref="T:System.Data.Common.CommandTrees.DbVariableReferenceExpression"/>, we create a nested query in which we alias the arguments to the aggregates. That is due to the following two limitations of Sql Server: <list type="number"> <item>If an expression being aggregated contains an outer reference, then that outer reference must be the only column referenced in the expression </item> <item>Sql Server cannot perform an aggregate function on an expression containing an aggregate or a subquery. </item> </list> The default translation, without inner query is: SELECT kexp1 AS key1, kexp2 AS key2,... kexpn AS keyn, aggf1(aexpr1) AS agg1, .. aggfn(aexprn) AS aggn FROM input AS a GROUP BY kexp1, kexp2, .. kexpn When we inject an innner query, the equivalent translation is: SELECT key1 AS key1, key2 AS key2, .. keyn AS keys, aggf1(agg1) AS agg1, aggfn(aggn) AS aggn FROM ( SELECT kexp1 AS key1, kexp2 AS key2,... kexpn AS keyn, aexpr1 AS agg1, .. aexprn AS aggn FROM input AS a ) as a GROUP BY key1, key2, keyn </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIntersectExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbUnionAllExpression)"/> </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIsEmptyExpression)"> <summary> Not(IsEmpty) has to be handled specially, so we delegate to <see cref="M:System.Data.SQLite.SqlGenerator.VisitIsEmptyExpression(System.Data.Common.CommandTrees.DbIsEmptyExpression,System.Boolean)"/>. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/>. <code>[NOT] EXISTS( ... )</code> </returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIsNullExpression)"> <summary> Not(IsNull) is handled specially, so we delegate to <see cref="M:System.Data.SQLite.SqlGenerator.VisitIsNullExpression(System.Data.Common.CommandTrees.DbIsNullExpression,System.Boolean)"/> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/> <code>IS [NOT] NULL</code> </returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIsOfExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbIsOfExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbCrossJoinExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.VisitJoinExpression(System.Collections.Generic.IList{System.Data.Common.CommandTrees.DbExpressionBinding},System.Data.Common.CommandTrees.DbExpressionKind,System.String,System.Data.Common.CommandTrees.DbExpression)"/> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/>.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbJoinExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.VisitJoinExpression(System.Collections.Generic.IList{System.Data.Common.CommandTrees.DbExpressionBinding},System.Data.Common.CommandTrees.DbExpressionKind,System.String,System.Data.Common.CommandTrees.DbExpression)"/> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/>.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbLikeExpression)"> <summary> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbLimitExpression)"> <summary> Translates to TOP expression. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbNewInstanceExpression)"> <summary> DbNewInstanceExpression is allowed as a child of DbProjectExpression only. If anyone else is the parent, we throw. We also perform special casing for collections - where we could convert them into Unions <see cref="M:System.Data.SQLite.SqlGenerator.VisitNewInstanceExpression(System.Data.Common.CommandTrees.DbNewInstanceExpression)"/> for the actual implementation. </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbNotExpression)"> <summary> The Not expression may cause the translation of its child to change. These children are <list type="bullet"> <item><see cref="T:System.Data.Common.CommandTrees.DbNotExpression"/>NOT(Not(x)) becomes x</item> <item><see cref="T:System.Data.Common.CommandTrees.DbIsEmptyExpression"/>NOT EXISTS becomes EXISTS</item> <item><see cref="T:System.Data.Common.CommandTrees.DbIsNullExpression"/>IS NULL becomes IS NOT NULL</item> <item><see cref="T:System.Data.Common.CommandTrees.DbComparisonExpression"/>= becomes<> </item> </list> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbNullExpression)"> <summary> </summary> <param name="e"></param> <returns><see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbOfTypeExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbOfTypeExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbOrExpression)"> <summary> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> <seealso cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbAndExpression)"/> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbParameterReferenceExpression)"> <summary> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbProjectExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"/> for the general ideas. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/></returns> <seealso cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"/> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbPropertyExpression)"> <summary> This method handles record flattening, which works as follows. consider an expression <c>Prop(y, Prop(x, Prop(d, Prop(c, Prop(b, Var(a)))))</c> where a,b,c are joins, d is an extent and x and y are fields. b has been flattened into a, and has its own SELECT statement. c has been flattened into b. d has been flattened into c. We visit the instance, so we reach Var(a) first. This gives us a (join)symbol. Symbol(a).b gives us a join symbol, with a SELECT statement i.e. Symbol(b). From this point on , we need to remember Symbol(b) as the source alias, and then try to find the column. So, we use a SymbolPair. We have reached the end when the symbol no longer points to a join symbol. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.JoinSymbol"/> if we have not reached the first Join node that has a SELECT statement. A <see cref="T:System.Data.SQLite.SymbolPair"/> if we have seen the JoinNode, and it has a SELECT statement. A <see cref="T:System.Data.SQLite.SqlBuilder"/> with {Input}.propertyName otherwise. </returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbQuantifierExpression)"> <summary> Any(input, x) => Exists(Filter(input,x)) All(input, x) => Not Exists(Filter(input, not(x)) </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbRefExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbRefExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbRelationshipNavigationExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbRelationshipNavigationExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbSkipExpression)"> <summary> For Sql9 it translates to: SELECT Y.x1, Y.x2, ..., Y.xn FROM ( SELECT X.x1, X.x2, ..., X.xn, row_number() OVER (ORDER BY sk1, sk2, ...) AS [row_number] FROM input as X ) as Y WHERE Y.[row_number] > count ORDER BY sk1, sk2, ... </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbSortExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"/> </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/></returns> <seealso cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"/> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbTreatExpression)"> <summary> <see cref="T:System.Data.Common.CommandTrees.DbTreatExpression"/> is illegal at this stage </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbUnionAllExpression)"> <summary> This code is shared by <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbExceptExpression)"/> and <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIntersectExpression)"/> <see cref="M:System.Data.SQLite.SqlGenerator.VisitSetOpExpression(System.Data.Common.CommandTrees.DbExpression,System.Data.Common.CommandTrees.DbExpression,System.String)"/> Since the left and right expression may not be Sql select statements, we must wrap them up to look like SQL select statements. </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbVariableReferenceExpression)"> <summary> This method determines whether an extent from an outer scope(free variable) is used in the CurrentSelectStatement. An extent in an outer scope, if its symbol is not in the FromExtents of the CurrentSelectStatement. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.Symbol"/>.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitAggregate(System.Data.Common.CommandTrees.DbAggregate,System.Object)"> <summary> Aggregates are not visited by the normal visitor walk. </summary> <param name="aggregate">The aggreate to be translated</param> <param name="aggregateArgument">The translated aggregate argument</param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitInputExpression(System.Data.Common.CommandTrees.DbExpression,System.String,System.Data.Metadata.Edm.TypeUsage,System.Data.SQLite.Symbol@)"> <summary> This is called by the relational nodes. It does the following <list> <item>If the input is not a SqlSelectStatement, it assumes that the input is a collection expression, and creates a new SqlSelectStatement </item> </list> </summary> <param name="inputExpression"></param> <param name="inputVarName"></param> <param name="inputVarType"></param> <param name="fromSymbol"></param> <returns>A <see cref="T:System.Data.SQLite.SqlSelectStatement"/> and the main fromSymbol for this select statement.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitIsEmptyExpression(System.Data.Common.CommandTrees.DbIsEmptyExpression,System.Boolean)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIsEmptyExpression)"/> </summary> <param name="e"></param> <param name="negate">Was the parent a DbNotExpression?</param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitCollectionConstructor(System.Data.Common.CommandTrees.DbNewInstanceExpression)"> <summary> Translate a NewInstance(Element(X)) expression into "select top(1) * from X" </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitIsNullExpression(System.Data.Common.CommandTrees.DbIsNullExpression,System.Boolean)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIsNullExpression)"/> </summary> <param name="e"></param> <param name="negate">Was the parent a DbNotExpression?</param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitJoinExpression(System.Collections.Generic.IList{System.Data.Common.CommandTrees.DbExpressionBinding},System.Data.Common.CommandTrees.DbExpressionKind,System.String,System.Data.Common.CommandTrees.DbExpression)"> <summary> This handles the processing of join expressions. The extents on a left spine are flattened, while joins not on the left spine give rise to new nested sub queries. Joins work differently from the rest of the visiting, in that the parent (i.e. the join node) creates the SqlSelectStatement for the children to use. The "parameter" IsInJoinContext indicates whether a child extent should add its stuff to the existing SqlSelectStatement, or create a new SqlSelectStatement By passing true, we ask the children to add themselves to the parent join, by passing false, we ask the children to create new Select statements for themselves. This method is called from <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbApplyExpression)"/> and <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbJoinExpression)"/>. </summary> <param name="inputs"></param> <param name="joinKind"></param> <param name="joinString"></param> <param name="joinCondition"></param> <returns> A <see cref="T:System.Data.SQLite.SqlSelectStatement"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.ProcessJoinInputResult(System.Data.SQLite.ISqlFragment,System.Data.SQLite.SqlSelectStatement,System.Data.Common.CommandTrees.DbExpressionBinding,System.Int32)"> <summary> This is called from <see cref="M:System.Data.SQLite.SqlGenerator.VisitJoinExpression(System.Collections.Generic.IList{System.Data.Common.CommandTrees.DbExpressionBinding},System.Data.Common.CommandTrees.DbExpressionKind,System.String,System.Data.Common.CommandTrees.DbExpression)"/>. This is responsible for maintaining the symbol table after visiting a child of a join expression. The child's sql statement may need to be completed. The child's result could be one of <list type="number"> <item>The same as the parent's - this is treated specially.</item> <item>A sql select statement, which may need to be completed</item> <item>An extent - just copy it to the from clause</item> <item>Anything else (from a collection-valued expression) - unnest and copy it.</item> </list> If the input was a Join, we need to create a new join symbol, otherwise, we create a normal symbol. We then call AddFromSymbol to add the AS clause, and update the symbol table. If the child's result was the same as the parent's, we have to clean up the list of symbols in the FromExtents list, since this contains symbols from the children of both the parent and the child. The happens when the child visited is a Join, and is the leftmost child of the parent. </summary> <param name="fromExtentFragment"></param> <param name="result"></param> <param name="input"></param> <param name="fromSymbolStart"></param> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitNewInstanceExpression(System.Data.Common.CommandTrees.DbNewInstanceExpression)"> <summary> We assume that this is only called as a child of a Project. This replaces <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbNewInstanceExpression)"/>, since we do not allow DbNewInstanceExpression as a child of any node other than DbProjectExpression. We write out the translation of each of the columns in the record. </summary> <param name="e"></param> <returns>A <see cref="T:System.Data.SQLite.SqlBuilder"/></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsSpecialBuiltInFunction(System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Determines whether the given function is a built-in function that requires special handling </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsSpecialCanonicalFunction(System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Determines whether the given function is a canonical function that requires special handling </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleFunctionDefault(System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Default handling for functions Translates them to FunctionName(arg1, arg2, ..., argn) </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleFunctionDefaultGivenName(System.Data.Common.CommandTrees.DbFunctionExpression,System.String)"> <summary> Default handling for functions with a given name. Translates them to functionName(arg1, arg2, ..., argn) </summary> <param name="e"></param> <param name="functionName"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleFunctionArgumentsDefault(System.Data.Common.CommandTrees.DbFunctionExpression,System.Data.SQLite.SqlBuilder)"> <summary> Default handling on function arguments Appends the list of arguments to the given result If the function is niladic it does not append anything, otherwise it appends (arg1, arg2, ..., argn) </summary> <param name="e"></param> <param name="result"></param> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleSpecialBuiltInFunction(System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Handler for special built in functions </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleSpecialCanonicalFunction(System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Handler for special canonical functions </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleSpecialFunction(System.Collections.Generic.Dictionary{System.String,System.Data.SQLite.SqlGenerator.FunctionHandler},System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Dispatches the special function processing to the appropriate handler </summary> <param name="handlers"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleSpecialFunctionToOperator(System.Data.Common.CommandTrees.DbFunctionExpression,System.Boolean)"> <summary> Handles functions that are translated into TSQL operators. The given function should have one or two arguments. Functions with one arguemnt are translated into op arg Functions with two arguments are translated into arg0 op arg1 Also, the arguments can be optionaly enclosed in parethesis </summary> <param name="e"></param> <param name="parenthesiseArguments">Whether the arguments should be enclosed in parethesis</param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleConcatFunction(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.HandleSpecialFunctionToOperator(System.Data.Common.CommandTrees.DbFunctionExpression,System.Boolean)"></see> </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionBitwise(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.HandleSpecialFunctionToOperator(System.Data.Common.CommandTrees.DbFunctionExpression,System.Boolean)"></see> </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleDatepartDateFunction(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Handles special case in which datepart 'type' parameter is present. all the functions handles here have *only* the 1st parameter as datepart. datepart value is passed along the QP as string and has to be expanded as TSQL keyword. </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionDateAdd(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> DateAdd(datetime, secondsToAdd) -> DATEADD ( seconds , number, date) </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionDateSubtract(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> DateSubtract(datetime1, datetime2) -> DATEDIFF ( seconds , startdate , enddate ) </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionDatepart(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Handler for canonical functions for extracting date parts. For example: Year(date) -> DATEPART( year, date) </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionIndexOf(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Function rename IndexOf -> CHARINDEX </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionNewGuid(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Function rename NewGuid -> NEWID </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionLength(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Length(arg) -> LEN(arg + '.') - LEN('.') </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionRound(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Round(numericExpression) -> Round(numericExpression, 0); </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionTrim(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> TRIM(string) -> LTRIM(RTRIM(string)) </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionRight(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> RIGHT(string, length) -> SUBSTR(string, -(length), length) </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionToLower(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Function rename ToLower -> LOWER </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCanonicalFunctionToUpper(System.Data.SQLite.SqlGenerator,System.Data.Common.CommandTrees.DbFunctionExpression)"> <summary> Function rename ToUpper -> UPPER </summary> <param name="sqlgen"></param> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.AddColumns(System.Data.SQLite.SqlSelectStatement,System.Data.SQLite.Symbol,System.Collections.Generic.List{System.Data.SQLite.Symbol},System.Collections.Generic.Dictionary{System.String,System.Data.SQLite.Symbol},System.String@)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.AddDefaultColumns(System.Data.SQLite.SqlSelectStatement)"/> Add the column names from the referenced extent/join to the select statement. If the symbol is a JoinSymbol, we recursively visit all the extents, halting at real extents and JoinSymbols that have an associated SqlSelectStatement. The column names for a real extent can be derived from its type. The column names for a Join Select statement can be got from the list of columns that was created when the Join's select statement was created. We do the following for each column. <list type="number"> <item>Add the SQL string for each column to the SELECT clause</item> <item>Add the column to the list of columns - so that it can become part of the "type" of a JoinSymbol</item> <item>Check if the column name collides with a previous column added to the same select statement. Flag both the columns for renaming if true.</item> <item>Add the column to a name lookup dictionary for collision detection.</item> </list> </summary> <param name="selectStatement">The select statement that started off as SELECT *</param> <param name="symbol">The symbol containing the type information for the columns to be added.</param> <param name="columnList">Columns that have been added to the Select statement. This is created in <see cref="M:System.Data.SQLite.SqlGenerator.AddDefaultColumns(System.Data.SQLite.SqlSelectStatement)"/>.</param> <param name="columnDictionary">A dictionary of the columns above.</param> <param name="separator">Comma or nothing, depending on whether the SELECT clause is empty.</param> </member> <member name="M:System.Data.SQLite.SqlGenerator.AddDefaultColumns(System.Data.SQLite.SqlSelectStatement)"> <summary> Expands Select * to "select the_list_of_columns" If the columns are taken from an extent, they are written as {original_column_name AS Symbol(original_column)} to allow renaming. If the columns are taken from a Join, they are written as just {original_column_name}, since there cannot be a name collision. We concatenate the columns from each of the inputs to the select statement. Since the inputs may be joins that are flattened, we need to recurse. The inputs are inferred from the symbols in FromExtents. </summary> <param name="selectStatement"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.AddFromSymbol(System.Data.SQLite.SqlSelectStatement,System.String,System.Data.SQLite.Symbol)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.AddFromSymbol(System.Data.SQLite.SqlSelectStatement,System.String,System.Data.SQLite.Symbol,System.Boolean)"/> </summary> <param name="selectStatement"></param> <param name="inputVarName"></param> <param name="fromSymbol"></param> </member> <member name="M:System.Data.SQLite.SqlGenerator.AddFromSymbol(System.Data.SQLite.SqlSelectStatement,System.String,System.Data.SQLite.Symbol,System.Boolean)"> <summary> This method is called after the input to a relational node is visited. <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbProjectExpression)"/> and <see cref="M:System.Data.SQLite.SqlGenerator.ProcessJoinInputResult(System.Data.SQLite.ISqlFragment,System.Data.SQLite.SqlSelectStatement,System.Data.Common.CommandTrees.DbExpressionBinding,System.Int32)"/> There are 2 scenarios <list type="number"> <item>The fromSymbol is new i.e. the select statement has just been created, or a join extent has been added.</item> <item>The fromSymbol is old i.e. we are reusing a select statement.</item> </list> If we are not reusing the select statement, we have to complete the FROM clause with the alias <code> -- if the input was an extent FROM = [SchemaName].[TableName] -- if the input was a Project FROM = (SELECT ... FROM ... WHERE ...) </code> These become <code> -- if the input was an extent FROM = [SchemaName].[TableName] AS alias -- if the input was a Project FROM = (SELECT ... FROM ... WHERE ...) AS alias </code> and look like valid FROM clauses. Finally, we have to add the alias to the global list of aliases used, and also to the current symbol table. </summary> <param name="selectStatement"></param> <param name="inputVarName">The alias to be used.</param> <param name="fromSymbol"></param> <param name="addToSymbolTable"></param> </member> <member name="M:System.Data.SQLite.SqlGenerator.AddSortKeys(System.Data.SQLite.SqlBuilder,System.Collections.Generic.IList{System.Data.Common.CommandTrees.DbSortClause})"> <summary> Translates a list of SortClauses. Used in the translation of OrderBy </summary> <param name="orderByClause">The SqlBuilder to which the sort keys should be appended</param> <param name="sortKeys"></param> </member> <member name="M:System.Data.SQLite.SqlGenerator.CreateNewSelectStatement(System.Data.SQLite.SqlSelectStatement,System.String,System.Data.Metadata.Edm.TypeUsage,System.Data.SQLite.Symbol@)"> <summary> <see cref="M:System.Data.SQLite.SqlGenerator.CreateNewSelectStatement(System.Data.SQLite.SqlSelectStatement,System.String,System.Data.Metadata.Edm.TypeUsage,System.Boolean,System.Data.SQLite.Symbol@)"/> </summary> <param name="oldStatement"></param> <param name="inputVarName"></param> <param name="inputVarType"></param> <param name="fromSymbol"></param> <returns>A new select statement, with the old one as the from clause.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.CreateNewSelectStatement(System.Data.SQLite.SqlSelectStatement,System.String,System.Data.Metadata.Edm.TypeUsage,System.Boolean,System.Data.SQLite.Symbol@)"> <summary> This is called after a relational node's input has been visited, and the input's sql statement cannot be reused. <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbProjectExpression)"/> When the input's sql statement cannot be reused, we create a new sql statement, with the old one as the from clause of the new statement. The old statement must be completed i.e. if it has an empty select list, the list of columns must be projected out. If the old statement being completed has a join symbol as its from extent, the new statement must have a clone of the join symbol as its extent. We cannot reuse the old symbol, but the new select statement must behave as though it is working over the "join" record. </summary> <param name="oldStatement"></param> <param name="inputVarName"></param> <param name="inputVarType"></param> <param name="finalizeOldStatement"></param> <param name="fromSymbol"></param> <returns>A new select statement, with the old one as the from clause.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.EscapeSingleQuote(System.String,System.Boolean)"> <summary> Before we embed a string literal in a SQL string, we should convert all ' to '', and enclose the whole string in single quotes. </summary> <param name="s"></param> <param name="isUnicode"></param> <returns>The escaped sql string.</returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.GetSqlPrimitiveType(System.Data.Metadata.Edm.TypeUsage)"> <summary> Returns the sql primitive/native type name. It will include size, precision or scale depending on type information present in the type facets </summary> <param name="type"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.HandleCountExpression(System.Data.Common.CommandTrees.DbExpression)"> <summary> Handles the expression represending DbLimitExpression.Limit and DbSkipExpression.Count. If it is a constant expression, it simply does to string thus avoiding casting it to the specific value (which would be done if <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbConstantExpression)"/> is called) </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsApplyExpression(System.Data.Common.CommandTrees.DbExpression)"> <summary> This is used to determine if a particular expression is an Apply operation. This is only the case when the DbExpressionKind is CrossApply or OuterApply. </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsJoinExpression(System.Data.Common.CommandTrees.DbExpression)"> <summary> This is used to determine if a particular expression is a Join operation. This is true for DbCrossJoinExpression and DbJoinExpression, the latter of which may have one of several different ExpressionKinds. </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsComplexExpression(System.Data.Common.CommandTrees.DbExpression)"> <summary> This is used to determine if a calling expression needs to place round brackets around the translation of the expression e. Constants, parameters and properties do not require brackets, everything else does. </summary> <param name="e"></param> <returns>true, if the expression needs brackets </returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsCompatible(System.Data.SQLite.SqlSelectStatement,System.Data.Common.CommandTrees.DbExpressionKind)"> <summary> Determine if the owner expression can add its unique sql to the input's SqlSelectStatement </summary> <param name="result">The SqlSelectStatement of the input to the relational node.</param> <param name="expressionKind">The kind of the expression node(not the input's)</param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.QuoteIdentifier(System.String)"> <summary> We use the normal box quotes for SQL server. We do not deal with ANSI quotes i.e. double quotes. </summary> <param name="name"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitExpressionEnsureSqlStatement(System.Data.Common.CommandTrees.DbExpression)"> <summary> Simply calls <see cref="M:System.Data.SQLite.SqlGenerator.VisitExpressionEnsureSqlStatement(System.Data.Common.CommandTrees.DbExpression,System.Boolean)"/> with addDefaultColumns set to true </summary> <param name="e"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitExpressionEnsureSqlStatement(System.Data.Common.CommandTrees.DbExpression,System.Boolean)"> <summary> This is called from <see cref="M:System.Data.SQLite.SqlGenerator.GenerateSql(System.Data.Common.CommandTrees.DbQueryCommandTree)"/> and nodes which require a select statement as an argument e.g. <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbIsEmptyExpression)"/>, <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbUnionAllExpression)"/>. SqlGenerator needs its child to have a proper alias if the child is just an extent or a join. The normal relational nodes result in complete valid SQL statements. For the rest, we need to treat them as there was a dummy <code> -- originally {expression} -- change that to SELECT * FROM {expression} as c </code> DbLimitExpression needs to start the statement but not add the default columns </summary> <param name="e"></param> <param name="addDefaultColumns"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.VisitFilterExpression(System.Data.Common.CommandTrees.DbExpressionBinding,System.Data.Common.CommandTrees.DbExpression,System.Boolean)"> <summary> This method is called by <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbFilterExpression)"/> and <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbQuantifierExpression)"/> </summary> <param name="input"></param> <param name="predicate"></param> <param name="negatePredicate">This is passed from <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbQuantifierExpression)"/> in the All(...) case.</param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.WrapNonQueryExtent(System.Data.SQLite.SqlSelectStatement,System.Data.SQLite.ISqlFragment,System.Data.Common.CommandTrees.DbExpressionKind)"> <summary> If the sql fragment for an input expression is not a SqlSelect statement or other acceptable form (e.g. an extent as a SqlBuilder), we need to wrap it in a form acceptable in a FROM clause. These are primarily the <list type="bullet"> <item>The set operation expressions - union all, intersect, except</item> <item>TVFs, which are conceptually similar to tables</item> </list> </summary> <param name="result"></param> <param name="sqlFragment"></param> <param name="expressionKind"></param> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsBuiltinFunction(System.Data.Metadata.Edm.EdmFunction)"> <summary> Is this a builtin function (ie) does it have the builtinAttribute specified? </summary> <param name="function"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.WriteFunctionName(System.Data.SQLite.SqlBuilder,System.Data.Metadata.Edm.EdmFunction)"> <summary> </summary> <param name="function"></param> <param name="result"></param> </member> <member name="M:System.Data.SQLite.SqlGenerator.NeedsInnerQuery(System.Collections.Generic.IList{System.Data.Common.CommandTrees.DbAggregate})"> <summary> Helper method for the Group By visitor Returns true if at least one of the aggregates in the given list has an argument that is not a <see cref="T:System.Data.Common.CommandTrees.DbPropertyExpression"/> over <see cref="T:System.Data.Common.CommandTrees.DbVariableReferenceExpression"/> </summary> <param name="aggregates"></param> <returns></returns> </member> <member name="M:System.Data.SQLite.SqlGenerator.IsPropertyOverVarRef(System.Data.Common.CommandTrees.DbExpression)"> <summary> Determines whether the given expression is a <see cref="T:System.Data.Common.CommandTrees.DbPropertyExpression"/> over <see cref="T:System.Data.Common.CommandTrees.DbVariableReferenceExpression"/> </summary> <param name="expression"></param> <returns></returns> </member> <member name="P:System.Data.SQLite.SqlGenerator.CurrentSelectStatement"> <summary> The top of the stack </summary> </member> <member name="P:System.Data.SQLite.SqlGenerator.IsParentAJoin"> <summary> The top of the stack </summary> </member> <member name="T:System.Data.SQLite.SqlSelectStatement"> <summary> A SqlSelectStatement represents a canonical SQL SELECT statement. It has fields for the 5 main clauses <list type="number"> <item>SELECT</item> <item>FROM</item> <item>WHERE</item> <item>GROUP BY</item> <item>ORDER BY</item> </list> We do not have HAVING, since it does not correspond to anything in the DbCommandTree. Each of the fields is a SqlBuilder, so we can keep appending SQL strings or other fragments to build up the clause. We have a IsDistinct property to indicate that we want distict columns. This is given out of band, since the input expression to the select clause may already have some columns projected out, and we use append-only SqlBuilders. The DISTINCT is inserted when we finally write the object into a string. Also, we have a Top property, which is non-null if the number of results should be limited to certain number. It is given out of band for the same reasons as DISTINCT. The FromExtents contains the list of inputs in use for the select statement. There is usually just one element in this - Select statements for joins may temporarily have more than one. If the select statement is created by a Join node, we maintain a list of all the extents that have been flattened in the join in AllJoinExtents <example> in J(j1= J(a,b), c) FromExtents has 2 nodes JoinSymbol(name=j1, ...) and Symbol(name=c) AllJoinExtents has 3 nodes Symbol(name=a), Symbol(name=b), Symbol(name=c) </example> If any expression in the non-FROM clause refers to an extent in a higher scope, we add that extent to the OuterExtents list. This list denotes the list of extent aliases that may collide with the aliases used in this select statement. It is set by <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbVariableReferenceExpression)"/>. An extent is an outer extent if it is not one of the FromExtents. </summary> </member> <member name="M:System.Data.SQLite.SqlSelectStatement.WriteSql(System.Data.SQLite.SqlWriter,System.Data.SQLite.SqlGenerator)"> <summary> Write out a SQL select statement as a string. We have to <list type="number"> <item>Check whether the aliases extents we use in this statement have to be renamed. We first create a list of all the aliases used by the outer extents. For each of the FromExtents( or AllJoinExtents if it is non-null), rename it if it collides with the previous list. </item> <item>Write each of the clauses (if it exists) as a string</item> </list> </summary> <param name="writer"></param> <param name="sqlGenerator"></param> </member> <member name="P:System.Data.SQLite.SqlSelectStatement.IsDistinct"> <summary> Do we need to add a DISTINCT at the beginning of the SELECT </summary> </member> <member name="T:System.Data.SQLite.SqlWriter"> <summary> This extends StringWriter primarily to add the ability to add an indent to each line that is written out. </summary> </member> <member name="M:System.Data.SQLite.SqlWriter.#ctor(System.Text.StringBuilder)"> <summary> </summary> <param name="b"></param> </member> <member name="M:System.Data.SQLite.SqlWriter.Write(System.String)"> <summary> Reset atBeginningofLine if we detect the newline string. <see cref="M:System.Data.SQLite.SqlBuilder.AppendLine"/> Add as many tabs as the value of indent if we are at the beginning of a line. </summary> <param name="value"></param> </member> <member name="M:System.Data.SQLite.SqlWriter.WriteLine"> <summary> </summary> </member> <member name="P:System.Data.SQLite.SqlWriter.Indent"> <summary> The number of tabs to be added at the beginning of each new line. </summary> </member> <member name="T:System.Data.SQLite.SymbolPair"> <summary> The SymbolPair exists to solve the record flattening problem. <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbPropertyExpression)"/> Consider a property expression D(v, "j3.j2.j1.a.x") where v is a VarRef, j1, j2, j3 are joins, a is an extent and x is a columns. This has to be translated eventually into {j'}.{x'} The source field represents the outermost SqlStatement representing a join expression (say j2) - this is always a Join symbol. The column field keeps moving from one join symbol to the next, until it stops at a non-join symbol. This is returned by <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbPropertyExpression)"/>, but never makes it into a SqlBuilder. </summary> </member> <member name="T:System.Data.SQLite.SymbolTable"> <summary> The symbol table is quite primitive - it is a stack with a new entry for each scope. Lookups search from the top of the stack to the bottom, until an entry is found. The symbols are of the following kinds <list type="bullet"> <item><see cref="T:System.Data.SQLite.Symbol"/> represents tables (extents/nested selects/unnests)</item> <item><see cref="T:System.Data.SQLite.JoinSymbol"/> represents Join nodes</item> <item><see cref="T:System.Data.SQLite.Symbol"/> columns.</item> </list> Symbols represent names <see cref="M:System.Data.SQLite.SqlGenerator.Visit(System.Data.Common.CommandTrees.DbVariableReferenceExpression)"/> to be resolved, or things to be renamed. </summary> </member> <member name="T:System.Data.SQLite.TopClause"> <summary> TopClause represents the a TOP expression in a SqlSelectStatement. It has a count property, which indicates how many TOP rows should be selected and a boolen WithTies property. </summary> </member> <member name="M:System.Data.SQLite.TopClause.#ctor(System.Data.SQLite.ISqlFragment,System.Boolean)"> <summary> Creates a TopClause with the given topCount and withTies. </summary> <param name="topCount"></param> <param name="withTies"></param> </member> <member name="M:System.Data.SQLite.TopClause.#ctor(System.Int32,System.Boolean)"> <summary> Creates a TopClause with the given topCount and withTies. </summary> <param name="topCount"></param> <param name="withTies"></param> </member> <member name="M:System.Data.SQLite.TopClause.WriteSql(System.Data.SQLite.SqlWriter,System.Data.SQLite.SqlGenerator)"> <summary> Write out the TOP part of sql select statement It basically writes LIMIT (X). </summary> <param name="writer"></param> <param name="sqlGenerator"></param> </member> <member name="P:System.Data.SQLite.TopClause.WithTies"> <summary> Do we need to add a WITH_TIES to the top statement </summary> </member> <member name="P:System.Data.SQLite.TopClause.TopCount"> <summary> How many top rows should be selected. </summary> </member> <member name="T:System.Data.SQLite.SQLiteProviderManifest"> <summary> The Provider Manifest for SQL Server </summary> </member> <member name="M:System.Data.SQLite.SQLiteProviderManifest.#ctor(System.String)"> <summary> Constructs the provider manifest. </summary> <remarks> We pass the token as a DateTimeFormat enum text, because all the datetime functions are vastly different depending on how the user is opening the connection </remarks> <param name="manifestToken">A token used to infer the capabilities of the store</param> </member> <member name="M:System.Data.SQLite.SQLiteProviderManifest.GetDbInformation(System.String)"> <summary> Returns manifest information for the provider </summary> <param name="informationType">The name of the information to be retrieved.</param> <returns>An XmlReader at the begining of the information requested.</returns> </member> <member name="M:System.Data.SQLite.SQLiteProviderManifest.GetEdmType(System.Data.Metadata.Edm.TypeUsage)"> <summary> This method takes a type and a set of facets and returns the best mapped equivalent type in EDM. </summary> <param name="storeType">A TypeUsage encapsulating a store type and a set of facets</param> <returns>A TypeUsage encapsulating an EDM type and a set of facets</returns> </member> <member name="M:System.Data.SQLite.SQLiteProviderManifest.GetStoreType(System.Data.Metadata.Edm.TypeUsage)"> <summary> This method takes a type and a set of facets and returns the best mapped equivalent type </summary> <param name="edmType">A TypeUsage encapsulating an EDM type and a set of facets</param> <returns>A TypeUsage encapsulating a store type and a set of facets</returns> </member> <member name="M:System.Data.SQLite.SQLiteProviderServices.CreateSqlParameter(System.String,System.Data.Metadata.Edm.TypeUsage,System.Data.Metadata.Edm.ParameterMode,System.Object)"> <summary> Creates a SQLiteParameter given a name, type, and direction </summary> </member> <member name="M:System.Data.SQLite.SQLiteProviderServices.GetSqlDbType(System.Data.Metadata.Edm.TypeUsage,System.Boolean,System.Nullable{System.Int32}@)"> <summary> Determines DbType for the given primitive type. Extracts facet information as well. </summary> </member> <member name="M:System.Data.SQLite.SQLiteProviderServices.GetParameterSize(System.Data.Metadata.Edm.TypeUsage,System.Boolean)"> <summary> Determines preferred value for SqlParameter.Size. Returns null where there is no preference. </summary> </member> <member name="M:System.Data.SQLite.SQLiteProviderServices.GetStringDbType(System.Data.Metadata.Edm.TypeUsage)"> <summary> Chooses the appropriate DbType for the given string type. </summary> </member> <member name="M:System.Data.SQLite.SQLiteProviderServices.GetBinaryDbType(System.Data.Metadata.Edm.TypeUsage)"> <summary> Chooses the appropriate DbType for the given binary type. </summary> </member> <member name="M:System.Data.SQLite.SQLiteProviderServices.System#Data#SQLite#ISQLiteSchemaExtensions#BuildTempSchema(System.Data.SQLite.SQLiteConnection)"> <summary> Creates temporary tables on the connection so schema information can be queried </summary> <remarks> There's a lot of work involved in getting schema information out of SQLite, but LINQ expects to be able to query on schema tables. Therefore we need to "fake" it by generating temporary tables filled with the schema of the current connection. We get away with making this information static because schema information seems to always be queried on a new connection object, so the schema is always fresh. </remarks> <param name="cnn">The connection upon which to build the schema tables</param> </member> <member name="M:System.Data.SQLite.SQLiteProviderServices.DataTableToTable(System.Data.SQLite.SQLiteConnection,System.Data.DataTable,System.String)"> <summary> Turn a datatable into a table in the temporary database for the connection </summary> <param name="cnn">The connection to make the temporary table in</param> <param name="table">The table to write out</param> <param name="dest">The temporary table name to write to</param> </member> </members> </doc> |