Source

changelog / CHANGES_07

Full commit
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
1975
1976
1977
1978
1979
1980
1981
1982
1983
1984
1985
1986
1987
1988
1989
1990
1991
1992
1993
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
2025
2026
2027
2028
2029
2030
2031
2032
2033
2034
2035
2036
2037
2038
2039
2040
2041
2042
2043
2044
2045
2046
2047
2048
2049
2050
2051
2052
2053
2054
2055
2056
2057
2058
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2078
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
2092
2093
2094
2095
2096
2097
2098
2099
2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2112
2113
2114
2115
2116
2117
2118
2119
2120
2121
2122
2123
2124
2125
2126
2127
2128
2129
2130
2131
2132
2133
2134
2135
2136
2137
2138
2139
2140
2141
2142
2143
2144
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2157
2158
2159
2160
2161
2162
2163
2164
2165
2166
2167
2168
2169
2170
2171
2172
2173
2174
2175
2176
2177
2178
2179
2180
2181
2182
2183
2184
2185
2186
2187
2188
2189
2190
2191
2192
2193
2194
2195
2196
2197
2198
2199
2200
2201
2202
2203
2204
2205
2206
2207
2208
2209
2210
2211
2212
2213
2214
2215
2216
2217
2218
2219
2220
2221
2222
2223
2224
2225
2226
2227
2228
2229
2230
2231
2232
2233
2234
2235
2236
2237
2238
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2252
2253
2254
2255
2256
2257
2258
2259
2260
2261
2262
2263
2264
2265
2266
2267
2268
2269
2270
2271
2272
2273
2274
2275
2276
2277
2278
2279
2280
2281
2282
2283
2284
2285
2286
2287
2288
2289
2290
2291
2292
2293
2294
2295
2296
2297
2298
2299
2300
2301
2302
2303
2304
2305
2306
2307
2308
2309
2310
2311
2312
2313
2314
2315
2316
2317
2318
2319
2320
2321
2322
2323
2324
2325
2326
2327
2328
2329
2330
2331
2332
2333
2334
2335
2336
2337
2338
2339
2340
2341
2342
2343
2344
2345
2346
2347
2348
2349
2350
2351
2352
2353
2354
2355
2356
2357
2358
2359
2360
2361
2362
2363
2364
2365
2366
2367
2368
2369
2370
2371
2372
2373
2374
2375
2376
2377
2378
2379
2380
2381
2382
2383
2384
2385
2386
2387
2388
2389
2390
2391
2392
2393
2394
2395
2396
2397
2398
2399
2400
2401
2402
2403
2404
2405
2406
2407
2408
2409
2410
2411
2412
2413
2414
2415
2416
2417
2418
2419
2420
2421
2422
2423
2424
2425
2426
2427
2428
2429
2430
2431
2432
2433
2434
2435
2436
2437
2438
2439
2440
2441
2442
2443
2444
2445
2446
2447
2448
2449
2450
2451
2452
2453
2454
2455
2456
2457
2458
2459
2460
2461
2462
2463
2464
2465
2466
2467
2468
2469
2470
2471
2472
2473
2474
2475
2476
2477
2478
2479
2480
2481
2482
2483
2484
2485
2486
2487
2488
2489
2490
2491
2492
2493
2494
2495
2496
2497
2498
2499
2500
2501
2502
2503
2504
2505
2506
2507
2508
2509
2510
2511
2512
2513
2514
2515
2516
2517
2518
2519
2520
2521
2522
2523
2524
2525
2526
2527
2528
2529
2530
2531
2532
2533
2534
2535
2536
2537
2538
2539
2540
2541
2542
2543
2544
2545
2546
2547
2548
2549
2550
2551
2552
2553
2554
2555
2556
2557
2558
2559
2560
2561
2562
2563
2564
2565
2566
2567
2568
2569
2570
2571
2572
2573
2574
2575
2576
2577
2578
2579
2580
2581
2582
2583
2584
2585
2586
2587
2588
2589
2590
2591
2592
2593
2594
2595
2596
2597
2598
2599
2600
2601
2602
2603
2604
2605
2606
2607
2608
2609
2610
2611
2612
2613
2614
2615
2616
2617
2618
2619
2620
2621
2622
2623
2624
2625
2626
2627
2628
2629
2630
2631
2632
2633
2634
2635
2636
2637
2638
2639
2640
2641
2642
2643
2644
2645
2646
2647
2648
2649
2650
2651
2652
2653
2654
2655
2656
2657
2658
2659
2660
2661
2662
2663
2664
2665
2666
2667
2668
2669
2670
2671
2672
2673
2674
2675
2676
2677
2678
2679
2680
2681
2682
2683
2684
2685
2686
2687
2688
2689
2690
2691
2692
2693
2694
2695
2696
2697
2698
2699
2700
2701
2702
2703
2704
2705
2706
2707
2708
2709
2710
2711
2712
2713
2714
2715
2716
2717
2718
2719
2720
2721
2722
2723
2724
2725
2726
2727
2728
2729
2730
2731
2732
2733
2734
2735
2736
2737
2738
2739
2740
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2758
2759
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2770
2771
2772
2773
2774
2775
2776
2777
2778
2779
2780
2781
2782
2783
2784
2785
2786
2787
2788
2789
2790
2791
2792
2793
2794
2795
2796
2797
2798
2799
2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2824
2825
2826
2827
2828
2829
2830
2831
2832
2833
2834
2835
2836
2837
2838
2839
2840
2841
2842
2843
2844
2845
2846
2847
-*- coding: utf-8; fill-column: 68 -*-

=======
CHANGES
=======
0.7.10
======
- orm
  - [bug] Fixed Session accounting bug whereby replacing
    a deleted object in the identity map with another
    object of the same primary key would raise a
    "conflicting state" error on rollback(),
    if the replaced primary key were established either
    via non-unitofwork-established INSERT statement
    or by primary key switch of another instance.
    [ticket:2583]

- oracle
  - [bug] changed the list of cx_oracle types that are
    excluded from the setinputsizes() step to only include
    STRING and UNICODE; CLOB and NCLOB are removed.  This
    is to work around cx_oracle behavior which is broken
    for the executemany() call.  In 0.8, this same change
    is applied however it is also configurable via the
    exclude_setinputsizes argument. [ticket:2561]

- mysql
  - [feature] Added "raise_on_warnings" flag to OurSQL
    dialect.  [ticket:2523]

  - [feature] Added "read_timeout" flag to MySQLdb
    dialect.  [ticket:2554]

0.7.9
=====
- orm
  - [bug] Fixed bug mostly local to new
    AbstractConcreteBase helper where the "type"
    attribute from the superclass would not
    be overridden on the subclass to produce the
    "reserved for base" error message, instead placing
    a do-nothing attribute there.  This was inconsistent
    vs. using ConcreteBase as well as all the behavior
    of classical concrete mappings, where the "type"
    column from the polymorphic base would be explicitly
    disabled on subclasses, unless overridden
    explicitly.

  - [bug] A warning is emitted when lazy='dynamic'
    is combined with uselist=False.  This is an
    exception raise in 0.8.

  - [bug] Fixed bug whereby user error in related-object
    assignment could cause recursion overflow if the
    assignment triggered a backref of the same name
    as a bi-directional attribute on the incorrect
    class to the same target.  An informative
    error is raised now.

  - [bug] Fixed bug where incorrect type information
    would be passed when the ORM would bind the
    "version" column, when using the "version" feature.
    Tests courtesy Daniel Miller.  [ticket:2539]

  - [bug] Extra logic has been added to the "flush"
    that occurs within Session.commit(), such that the
    extra state added by an after_flush() or
    after_flush_postexec() hook is also flushed in a
    subsequent flush, before the "commit" completes.
    Subsequent calls to flush() will continue until
    the after_flush hooks stop adding new state.
    An "overflow" counter of 100 is also in place,
    in the event of a broken after_flush() hook
    adding new content each time. [ticket:2566]

- sql
  - [bug] Fixed the DropIndex construct to support
    an Index associated with a Table in a remote
    schema. [ticket:2571]

  - [bug] Fixed bug in over() construct whereby
    passing an empty list for either partition_by
    or order_by, as opposed to None, would fail
    to generate correctly.
    Courtesy Gunnlaugur Þór Briem.
    [ticket:2574]

  - [bug] Fixed CTE bug whereby positional
    bound parameters present in the CTEs themselves
    would corrupt the overall ordering of
    bound parameters.  This primarily
    affected SQL Server as the platform with
    positional binds + CTE support.
    [ticket:2521]

  - [bug] Fixed more un-intuitivenesses in CTEs
    which prevented referring to a CTE in a union
    of itself without it being aliased.
    CTEs now render uniquely
    on name, rendering the outermost CTE of a given
    name only - all other references are rendered
    just as the name.   This even includes other
    CTE/SELECTs that refer to different versions
    of the same CTE object, such as a SELECT
    or a UNION ALL of that SELECT. We are
    somewhat loosening the usual link between object
    identity and lexical identity in this case.
    A true name conflict between two unrelated
    CTEs now raises an error.

  - [bug] quoting is applied to the column names
    inside the WITH RECURSIVE clause of a
    common table expression according to the
    quoting rules for the originating Column.
    [ticket:2512]

  - [bug] Fixed regression introduced in 0.7.6
    whereby the FROM list of a SELECT statement
    could be incorrect in certain "clone+replace"
    scenarios.  [ticket:2518]

  - [bug] Fixed bug whereby usage of a UNION
    or similar inside of an embedded subquery
    would interfere with result-column targeting,
    in the case that a result-column had the same
    ultimate name as a name inside the embedded
    UNION. [ticket:2552]

  - [bug] Fixed a regression since 0.6 regarding
    result-row targeting.   It should be possible
    to use a select() statement with string
    based columns in it, that is
    select(['id', 'name']).select_from('mytable'),
    and have this statement be targetable by
    Column objects with those names; this is the
    mechanism by which
    query(MyClass).from_statement(some_statement)
    works.  At some point the specific case of
    using select(['id']), which is equivalent to
    select([literal_column('id')]), stopped working
    here, so this has been re-instated and of
    course tested. [ticket:2558]

  - [bug] Added missing operators is_(), isnot()
    to the ColumnOperators base, so that these long-available
    operators are present as methods like all
    the other operators.  [ticket:2544]

- engine
  - [bug] Fixed bug whereby
    a disconnect detect + dispose that occurs
    when the QueuePool has threads waiting
    for connections would leave those
    threads waiting for the duration of
    the timeout on the old pool (or indefinitely
    if timeout was disabled).  The fix
    now notifies those waiters with a special
    exception case and has them move onto
    the new pool.  [ticket:2522]

  - [feature] Dramatic improvement in memory
    usage of the event system; instance-level
    collections are no longer created for a
    particular type of event until
    instance-level listeners are established
    for that event.  [ticket:2516]

  - [bug] Added gaerdbms import to mysql/__init__.py,
    the absense of which was preventing the new
    GAE dialect from being loaded.  [ticket:2529]

  - [bug] Fixed cextension bug whereby the
    "ambiguous column error" would fail to
    function properly if the given index were
    a Column object and not a string.
    Note there are still some column-targeting
    issues here which are fixed in 0.8.
    [ticket:2553]

  - [bug] Fixed the repr() of Enum to include
    the "name" and "native_enum" flags.  Helps
    Alembic autogenerate.

- sqlite
  - [bug] Adjusted a very old bugfix which attempted
    to work around a SQLite issue that itself was
    "fixed" as of sqlite 3.6.14, regarding quotes
    surrounding a table name when using
    the "foreign_key_list" pragma.  The fix has been
    adjusted to not interfere with quotes that
    are *actually in the name* of a column or table,
    to as much a degree as possible; sqlite still
    doesn't return the correct result for foreign_key_list()
    if the target table actually has quotes surrounding
    its name, as *part* of its name (i.e. """mytable""").
    [ticket:2568]

  - [bug] Adjusted column default reflection code to
    convert non-string values to string, to accommodate
    old SQLite versions that don't deliver
    default info as a string.  [ticket:2265]

  - [feature] Added support for the localtimestamp()
    SQL function implemented in SQLite, courtesy
    Richard Mitchell.

- postgresql
  - [bug] Columns in reflected primary key constraint
    are now returned in the order in which the constraint
    itself defines them, rather than how the table
    orders them.  Courtesy Gunnlaugur Þór Briem.
    [ticket:2531].

  - [bug] Added 'terminating connection' to the list
    of messages we use to detect a disconnect with PG, which
    appears to be present in some versions when the server
    is restarted.  [ticket:2570]

- mysql
  - [bug] Updated mysqlconnector interface to use
    updated "client flag" and "charset" APIs,
    courtesy David McNelis.

- mssql
  - [bug] Fixed compiler bug whereby using a correlated
    subquery within an ORDER BY would fail to render correctly
    if the stament also used LIMIT/OFFSET, due to mis-rendering
    within the ROW_NUMBER() OVER clause.  Fix courtesy
    sayap [ticket:2538]

  - [bug] Fixed compiler bug whereby a given
    select() would be modified if it had an "offset"
    attribute, causing the construct to not compile
    correctly a second time.  [ticket:2545]

  - [bug] Fixed bug where reflection of primary key constraint
    would double up columns if the same constraint/table
    existed in multiple schemas.

0.7.8
=====
- orm
  - [bug] Fixed bug whereby subqueryload() from
    a polymorphic mapping to a target would incur
    a new invocation of the query for each
    distinct class encountered in the polymorphic
    result.  [ticket:2480]

  - [bug] Fixed bug in declarative
    whereby the precedence of columns
    in a joined-table, composite
    column (typically for id) would fail to
    be correct if the columns contained
    names distinct from their attribute
    names.  This would cause things like
    primaryjoin conditions made against the
    entity attributes to be incorrect.  Related
    to [ticket:1892] as this was supposed
    to be part of that, this is [ticket:2491].

  - [feature] The 'objects' argument to
    flush() is no longer deprecated, as some
    valid use cases have been identified.

  - [bug] Fixed identity_key() function which
    was not accepting a scalar argument
    for the identity.  [ticket:2508].

  - [bug] Fixed bug whereby populate_existing
    option would not propagate to subquery
    eager loaders.  [ticket:2497].

- sql
  - [bug] added BIGINT to types.__all__,
    BIGINT, BINARY, VARBINARY to sqlalchemy
    module namespace, plus test to ensure
    this breakage doesn't occur again.
    [ticket:2499]

  - [bug] Repaired common table expression
    rendering to function correctly when the
    SELECT statement contains UNION or other
    compound expressions, courtesy btbuilder.
    [ticket:2490]

  - [bug] Fixed bug whereby append_column()
    wouldn't function correctly on a cloned
    select() construct, courtesy
    Gunnlaugur Þór Briem.  [ticket:2482]

- engine
  - [bug] Fixed memory leak in C version of
    result proxy whereby DBAPIs which don't deliver
    pure Python tuples for result rows would
    fail to decrement refcounts correctly.
    The most prominently affected DBAPI
    is pyodbc.  [ticket:2489]

  - [bug] Fixed bug affecting Py3K whereby
    string positional parameters passed to
    engine/connection execute() would fail to be
    interpreted correctly, due to __iter__
    being present on Py3K string.
    [ticket:2503].

- postgresql
  - [bug] removed unnecessary table clause when
    reflecting enums, [ticket:2510].  Courtesy
    Gunnlaugur Þór Briem.

- oracle
  - [bug] Added ROWID to oracle.*, [ticket:2483]

- mysql
  - [feature] Added a new dialect for Google App
    Engine.  Courtesy Richie Foreman. [ticket:2484]


0.7.7
=====
- orm
  - [bug] Fixed issue in unit of work
    whereby setting a non-None self-referential
    many-to-one relationship to None
    would fail to persist the change if the
    former value was not already loaded.
    [ticket:2477].

  - [feature] Added prefix_with() method
    to Query, calls upon select().prefix_with()
    to allow placement of MySQL SELECT
    directives in statements.  Courtesy
    Diana Clarke [ticket:2443]

  - [bug] Fixed bug in 0.7.6 introduced by
    [ticket:2409] whereby column_mapped_collection
    used against columns that were mapped as
    joins or other indirect selectables
    would fail to function.

  - [feature] Added new flag to @validates
    include_removes.  When True, collection
    remove and attribute del events
    will also be sent to the validation function,
    which accepts an additional argument
    "is_remove" when this flag is used.

  - [bug] Fixed bug whereby polymorphic_on
    column that's not otherwise mapped on the
    class would be incorrectly included
    in a merge() operation, raising an error.
    [ticket:2449]

  - [bug] Fixed bug in expression annotation
    mechanics which could lead to incorrect
    rendering of SELECT statements with aliases
    and joins, particularly when using
    column_property().  [ticket:2453]

  - [bug] Fixed bug which would prevent
    OrderingList from being pickleable
    [ticket:2454].  Courtesy Jeff Dairiki

  - [bug] Fixed bug in relationship comparisons
    whereby calling unimplemented methods like
    SomeClass.somerelationship.like() would
    produce a recursion overflow, instead
    of NotImplementedError.

- sql
  - [bug] Removed warning when Index is created
    with no columns; while this might not be what
    the user intended, it is a valid use case
    as an Index could be a placeholder for just an
    index of a certain name.

  - [feature] Added new connection event
    dbapi_error(). Is called for all DBAPI-level
    errors passing the original DBAPI exception
    before SQLAlchemy modifies the state
    of the cursor.

  - [bug] If conn.begin() fails when calling
    "with engine.begin()", the newly acquired
    Connection is closed explicitly before
    propagating the exception onward normally.

  - [bug] Add BINARY, VARBINARY to types.__all__,
    [ticket:2474]

- mssql
  - [feature] Added interim create_engine flag
    supports_unicode_binds to PyODBC dialect,
    to force whether or not the dialect
    passes Python unicode literals to PyODBC
    or not.

  - [bug] Repaired the use_scope_identity
    create_engine() flag when using the pyodbc
    dialect.  Previously this flag would be
    ignored if set to False.  When set to False,
    you'll get "SELECT @@identity" after each
    INSERT to get at the last inserted ID,
    for those tables which have "implicit_returning"
    set to False.

  - [bug] UPDATE..FROM syntax with SQL Server
    requires that the updated table be present
    in the FROM clause when an alias of that
    table is also present in the FROM clause.
    The updated table is now always present
    in the FROM, when FROM is present
    in the first place.  Courtesy sayap.
    [ticket:2468]

- postgresql
  - [feature] Added new for_update/with_lockmode()
    options for Postgresql: for_update="read"/
    with_lockmode("read"),
    for_update="read_nowait"/
    with_lockmode("read_nowait").
    These emit "FOR SHARE" and "FOR SHARE NOWAIT",
    respectively.  Courtesy Diana Clarke
    [ticket:2445]

  - [bug] removed unnecessary table clause
    when reflecting domains, [ticket:2473]


- mysql
  - [bug] Fixed bug whereby column name inside
    of "KEY" clause for autoincrement composite
    column with InnoDB would double quote a
    name that's a reserved word.  Courtesy Jeff
    Dairiki. [ticket:2460]

  - [bug] Fixed bug whereby get_view_names() for
    "information_schema" schema would fail
    to retrieve views marked as "SYSTEM VIEW".
    courtesy Matthew Turland.

  - [bug] Fixed bug whereby if cast() is used
    on a SQL expression whose type is not supported
    by cast() and therefore CAST isn't rendered by
    the dialect, the order of evaluation could change
    if the casted expression required that it be
    grouped; grouping is now applied to those
    expressions.  [ticket:2467]

- sqlite

  - [feature] Added SQLite execution option
    "sqlite_raw_colnames=True", will bypass
    attempts to remove "." from column names
    returned by SQLite cursor.description.
    [ticket:2475]

  - [bug] When the primary key column of a Table
    is replaced, such as via extend_existing,
    the "auto increment" column used by insert()
    constructs is reset.  Previously it would
    remain referring to the previous primary
    key column.  [ticket:2525]

0.7.6
=====
- orm
  - [bug] Fixed event registration bug
    which would primarily show up as
    events not being registered with
    sessionmaker() instances created
    after the event was associated
    with the Session class.  [ticket:2424]

  - [bug] Fixed bug whereby a primaryjoin
    condition with a "literal" in it would
    raise an error on compile with certain
    kinds of deeply nested expressions
    which also needed to render the same
    bound parameter name more than once.
    [ticket:2425]

  - [feature] Added "no_autoflush" context
    manager to Session, used with with:
    will temporarily disable autoflush.

  - [feature] Added cte() method to Query,
    invokes common table expression support
    from the Core (see below). [ticket:1859]

  - [bug] Removed the check for number of
    rows affected when doing a multi-delete
    against mapped objects.   If an ON DELETE
    CASCADE exists between two rows, we can't
    get an accurate rowcount from the DBAPI;
    this particular count is not supported
    on most DBAPIs in any case, MySQLdb
    is the notable case where it is.
    [ticket:2403]

  - [bug] Fixed bug whereby objects using
    attribute_mapped_collection or
    column_mapped_collection could not be
    pickled.  [ticket:2409]

  - [bug] Fixed bug whereby MappedCollection
    would not get the appropriate collection
    instrumentation if it were only used
    in a custom subclass that used
    @collection.internally_instrumented.
    [ticket:2406]

  - [bug] Fixed bug whereby SQL adaption mechanics
    would fail in a very nested scenario involving
    joined-inheritance, joinedload(), limit(), and a
    derived function in the columns clause.
    [ticket:2419]

  - [bug] Fixed the repr() for CascadeOptions to
    include refresh-expire.  Also reworked
    CascadeOptions to be a <frozenset>.
    [ticket:2417]

  - [feature] Added the ability to query for
    Table-bound column names when using
    query(sometable).filter_by(colname=value).
    [ticket:2400]

  - [bug] Improved the "declarative reflection"
    example to support single-table inheritance,
    multiple calls to prepare(), tables that
    are present in alternate schemas,
    establishing only a subset of classes
    as reflected.

  - [bug] Scaled back the test applied within
    flush() to check for UPDATE against partially
    NULL PK within one table to only actually
    happen if there's really an UPDATE to occur.
    [ticket:2390]

  - [bug] Fixed bug whereby if a method name
    conflicted with a column name, a
    TypeError would be raised when the mapper
    tried to inspect the __get__() method
    on the method object.  [ticket:2352]

- sql
  - [bug] Fixed memory leak in core which would
    occur when C extensions were used with
    particular types of result fetches,
    in particular when orm query.count()
    were called.  [ticket:2427]

  - [bug] Fixed issue whereby attribute-based
    column access on a row would raise
    AttributeError with non-C version,
    NoSuchColumnError with C version.  Now
    raises AttributeError in both cases.
    [ticket:2398]

  - [feature] Added support for SQL standard
    common table expressions (CTE), allowing
    SELECT objects as the CTE source (DML
    not yet supported).  This is invoked via
    the cte() method on any select() construct.
    [ticket:1859]

  - [bug] Added support for using the .key
    of a Column as a string identifier in a
    result set row.   The .key is currently
    listed as an "alternate" name for a column,
    and is superseded by the name of a column
    which has that key value as its regular name.
    For the next major release
    of SQLAlchemy we may reverse this precedence
    so that .key takes precedence, but this
    is not decided on yet.  [ticket:2392]

  - [bug] A warning is emitted when a not-present
    column is stated in the values() clause
    of an insert() or update() construct.
    Will move to an exception in 0.8.
    [ticket:2413]

  - [bug] A significant change to how labeling
    is applied to columns in SELECT statements
    allows "truncated" labels, that is label names
    that are generated in Python which exceed
    the maximum identifier length (note this is
    configurable via label_length on create_engine()),
    to be properly referenced when rendered inside
    of a subquery, as well as to be present
    in a result set row using their original
    in-Python names.   [ticket:2396]

  - [bug] Fixed bug in new "autoload_replace" flag
    which would fail to preserve the primary
    key constraint of the reflected table.
    [ticket:2402]

  - [bug] Index will raise when arguments passed
    cannot be interpreted as columns or expressions.
    Will warn when Index is created
    with no columns at all.  [ticket:2380]

- engine
  - [feature] Added "no_parameters=True" execution
    option for connections.   If no parameters
    are present, will pass the statement
    as cursor.execute(statement), thereby invoking
    the DBAPIs behavior when no parameter collection
    is present; for psycopg2 and mysql-python, this
    means not interpreting % signs in the string.
    This only occurs with this option, and not
    just if the param list is blank, as otherwise
    this would produce inconsistent behavior
    of SQL expressions that normally escape percent
    signs (and while compiling, can't know ahead of
    time if parameters will be present in
    some cases).  [ticket:2407]

  - [bug] Added execution_options() call to
    MockConnection (i.e., that used with
    strategy="mock") which acts as a pass through
    for arguments.

  - [feature] Added pool_reset_on_return argument
    to create_engine, allows control over
    "connection return" behavior.  Also added
    new arguments 'rollback', 'commit', None
    to pool.reset_on_return to allow more control
    over connection return activity. [ticket:2378]

  - [feature] Added some decent context managers
    to Engine, Connection:

        with engine.begin() as conn:
            <work with conn in a transaction>

    and:

        with engine.connect() as conn:
            <work with conn>

    Both close out the connection when done,
    commit or rollback transaction with errors
    on engine.begin().

- sqlite
  - [bug] Fixed bug in C extensions whereby
    string format would not be applied to a
    Numeric value returned as integer; this
    affected primarily SQLite which does
    not maintain numeric scale settings.
    [ticket:2432]

- mssql
  - [feature] Added support for MSSQL INSERT,
    UPDATE, and DELETE table hints, using
    new with_hint() method on UpdateBase.
    [ticket:2430]

- mysql
  - [feature] Added support for MySQL index and
    primary key constraint types
    (i.e. USING) via new mysql_using parameter
    to Index and PrimaryKeyConstraint,
    courtesy Diana Clarke.  [ticket:2386]

  - [feature] Added support for the "isolation_level"
    parameter to all MySQL dialects.  Thanks
    to mu_mind for the patch here. [ticket:2394]

- oracle
  - [feature] Added a new create_engine() flag
    coerce_to_decimal=False, disables the precision
    numeric handling which can add lots of overhead
    by converting all numeric values to
    Decimal.  [ticket:2399]

  - [bug] Added missing compilation support for
    LONG [ticket:2401]

  - [bug] Added 'LEVEL' to the list of reserved
    words for Oracle.  [ticket:2435]

- examples
  - [bug] Altered _params_from_query() function
    in Beaker example to pull bindparams from the
    fully compiled statement, as a quick means
    to get everything including subqueries in the
    columns clause, etc.

0.7.5 (January 28, 2012)
=====
- orm
  - [bug] Fixed issue where modified session state
    established after a failed flush would be committed
    as part of the subsequent transaction that
    begins automatically after manual call
    to rollback().   The state of the session is
    checked within rollback(), and if new state
    is present, a warning is emitted and
    restore_snapshot() is called a second time,
    discarding those changes. [ticket:2389]

  - [bug] Fixed regression from 0.7.4 whereby
    using an already instrumented column from a
    superclass as "polymorphic_on" failed to resolve
    the underlying Column.  [ticket:2345]

  - [bug] Raise an exception if xyzload_all() is
    used inappropriately with two non-connected
    relationships.  [ticket:2370]

  - [feature] Added "class_registry" argument to
    declarative_base().  Allows two or more declarative
    bases to share the same registry of class names.

  - [feature] query.filter() accepts multiple
    criteria which will join via AND, i.e.
    query.filter(x==y, z>q, ...)

  - [feature] Added new capability to relationship
    loader options to allow "default" loader strategies.
    Pass '*' to any of joinedload(), lazyload(),
    subqueryload(), or noload() and that becomes the
    loader strategy used for all relationships,
    except for those explicitly stated in the
    Query.  Thanks to up-and-coming contributor
    Kent Bower for an exhaustive and well
    written test suite !  [ticket:2351]

  - [bug] Fixed bug whereby event.listen(SomeClass)
    forced an entirely unnecessary compile of the
    mapper, making events very hard to set up
    at module import time (nobody noticed this ??)
    [ticket:2367]

  - [bug] Fixed bug whereby hybrid_property didn't
    work as a kw arg in any(), has().

  - Fixed regression from 0.6 whereby if
    "load_on_pending" relationship() flag were used
    where a non-"get()" lazy clause needed to be
    emitted on a pending object, it would fail
    to load.

  - [bug] ensure pickleability of all ORM exceptions
    for multiprocessing compatibility. [ticket:2371]

  - [bug] implemented standard "can't set attribute" /
    "can't delete attribute" AttributeError when
    setattr/delattr used on a hybrid that doesn't
    define fset or fdel. [ticket:2353]

  - [bug] Fixed bug where unpickled object didn't
    have enough of its state set up to work
    correctly within the unpickle() event established
    by the mutable object extension, if the object
    needed ORM attribute access within
    __eq__() or similar. [ticket:2362]

  - [bug] Fixed bug where "merge" cascade could
    mis-interpret an unloaded attribute, if the
    load_on_pending flag were used with
    relationship().  Thanks to Kent Bower
    for tests.  [ticket:2374]

  - [feature] New declarative reflection example
    added, illustrates how best to mix table reflection
    with declarative as well as uses some new features
    from [ticket:2356].

- sql
  - [feature] New reflection feature "autoload_replace";
    when set to False on Table, the Table can be autoloaded
    without existing columns being replaced.  Allows
    more flexible chains of Table construction/reflection
    to be constructed, including that it helps with
    combining Declarative with table reflection.
    See the new example on the wiki.  [ticket:2356]

  - [bug] Improved the API for add_column() such that
    if the same column is added to its own table,
    an error is not raised and the constraints
    don't get doubled up.  Also helps with some
    reflection/declarative patterns. [ticket:2356]

  - [feature] Added "false()" and "true()" expression
    constructs to sqlalchemy.sql namespace, though
    not part of __all__ as of yet.

  - [feature] Dialect-specific compilers now raise
    CompileException for all type/statement compilation
    issues, instead of InvalidRequestError or ArgumentError.
    The DDL for CREATE TABLE will re-raise
    CompileExceptions to include table/column information
    for the problematic column.  [ticket:2361]

  - [bug] Fixed issue where the "required" exception
    would not be raised for bindparam() with required=True,
    if the statement were given no parameters at all.
    [ticket:2381]

- engine
  - [bug] Added __reduce__ to StatementError,
    DBAPIError, column errors so that exceptions
    are pickleable, as when using multiprocessing.
    However, not
    all DBAPIs support this yet, such as
    psycopg2. [ticket:2371]

  - [bug] Improved error messages when a non-string
    or invalid string is passed to any of the
    date/time processors used by SQLite, including
    C and Python versions.  [ticket:2382]

  - [bug] Fixed bug whereby a table-bound Column
    object named "<a>_<b>" which matched a column
    labeled as "<tablename>_<colname>" could match
    inappropriately when targeting in a result
    set row.  [ticket:2377]

  - [bug] Fixed bug in "mock" strategy whereby
    correct DDL visit method wasn't called, resulting
    in "CREATE/DROP SEQUENCE" statements being
    duplicated [ticket:2384]

- sqlite
  - [bug] the "name" of an FK constraint in SQLite
    is reflected as "None", not "0" or other
    integer value [ticket:2364].
    SQLite does not appear to support constraint
    naming in any case.

  - [bug] sql.false() and sql.true() compile to
    0 and 1, respectively in sqlite [ticket:2368]

  - [bug] removed an erroneous "raise" in the
    SQLite dialect when getting table names
    and view names, where logic is in place
    to fall back to an older version of
    SQLite that doesn't have the
    "sqlite_temp_master" table.

- mysql
  - [bug] fixed regexp that filters out warnings
    for non-reflected "PARTITION" directives,
    thanks to George Reilly [ticket:2376]

- mssql
  - [bug] Adjusted the regexp used in the
    mssql.TIME type to ensure only six digits
    are received for the "microseconds" portion
    of the value, which is expected by
    Python's datetime.time().  Note that
    support for sending microseconds doesn't
    seem to be possible yet with pyodbc
    at least.  [ticket:2340]

  - [bug] Dropped the "30 char" limit on pymssql,
    based on reports that it's doing things
    better these days.  pymssql hasn't been
    well tested and as the DBAPI is in flux
    it's still not clear what the status
    is on this driver and how SQLAlchemy's
    implementation should adapt.  [ticket:2347]

- oracle
  - [bug] Added ORA-03135 to the never ending
    list of oracle "connection lost" errors
    [ticket:2388]

- core
  - [bug] Changed LRUCache, used by the mapper
    to cache INSERT/UPDATE/DELETE statements,
    to use an incrementing counter instead
    of a timestamp to track entries, for greater
    reliability versus using time.time(), which
    can cause test failures on some platforms.
    [ticket:2379]

  - [bug] Added a boolean check for the "finalize"
    function within the pool connection proxy's
    weakref callback before calling it, so that a
    warning isn't emitted that this function is None
    when the application is exiting and gc has
    removed the function from the module before the
    weakref callback was invoked.  [ticket:2383]

- Py3K
  - [bug] Fixed inappropriate usage of util.py3k
    flag and renamed it to util.py3k_warning, since
    this flag is intended to detect the -3 flag
    series of import restrictions only.
    [ticket:2348]

- examples
  - [feature] Simplified the versioning example
    a bit to use a declarative mixin as well
    as an event listener, instead of a metaclass +
    SessionExtension.  [ticket:2313]

  - [bug] Fixed large_collection.py to close the
    session before dropping tables. [ticket:2346]

0.7.4 (December 9, 2011)
=====
- orm
  - [bug] Fixed backref behavior when "popping" the
    value off of a many-to-one in response to
    a removal from a stale one-to-many - the operation
    is skipped, since the many-to-one has since
    been updated.  [ticket:2315]

  - [bug] After some years of not doing this, added
    more granularity to the "is X a parent of Y"
    functionality, which is used when determining
    if the FK on "Y" needs to be "nulled out" as well
    as if "Y" should be deleted with delete-orphan
    cascade.   The test now takes into account the
    Python identity of the parent as well its identity
    key, to see if the last known parent of Y is
    definitely X.   If a decision
    can't be made, a StaleDataError is raised.  The
    conditions where this error is raised are fairly
    rare, requiring that the previous parent was
    garbage collected, and previously
    could very well inappropriately update/delete
    a record that's since moved onto a new parent,
    though there may be some cases where
    "silent success" occurred previously that will now
    raise in the face of ambiguity.
    Expiring "Y" resets the "parent" tracker, meaning
    X.remove(Y) could then end up deleting Y even
    if X is stale, but this is the same behavior
    as before; it's advised to expire X also in that
    case.  [ticket:2264]

  - [bug] fixed inappropriate evaluation of user-mapped
    object in a boolean context within query.get()
    [ticket:2310].  Also in 0.6.9.

  - [bug] Added missing comma to PASSIVE_RETURN_NEVER_SET
    symbol [ticket:2304]

  - [bug] Cls.column.collate("some collation") now
    works.  [ticket:1776]  Also in 0.6.9

  - [bug] the value of a composite attribute is now
    expired after an insert or update operation, instead
    of regenerated in place.  This ensures that a
    column value which is expired within a flush
    will be loaded first, before the composite
    is regenerated using that value.  [ticket:2309]

  - [bug] The fix in [ticket:2309] also emits the
    "refresh" event when the composite value is
    loaded on access, even if all column
    values were already present, as is appropriate.
    This fixes the "mutable" extension which relies
    upon the "load" event to ensure the _parents
    dictionary is up to date, fixes [ticket:2308].
    Thanks to Scott Torborg for the test case here.

  - [bug] Fixed bug whereby a subclass of a subclass
    using concrete inheritance in conjunction with
    the new ConcreteBase or AbstractConcreteBase
    would fail to apply the subclasses deeper than
    one level to the "polymorphic loader" of each
    base  [ticket:2312]

  - [bug] Fixed bug whereby a subclass of a subclass
    using the new AbstractConcreteBase would fail
    to acquire the correct "base_mapper" attribute
    when the "base" mapper was generated, thereby
    causing failures later on.  [ticket:2312]

  - [bug] Fixed bug whereby column_property() created
    against ORM-level column could be treated as
    a distinct entity when producing certain
    kinds of joined-inh joins.  [ticket:2316]

  - [bug] Fixed the error formatting raised when
    a tuple is inadvertently passed to session.query()
    [ticket:2297].  Also in 0.6.9.

  - [bug] Calls to query.join() to a single-table
    inheritance subclass are now tracked, and
    are used to eliminate the additional WHERE..
    IN criterion normally tacked on with single
    table inheritance, since the join should
    accommodate it.  This allows OUTER JOIN
    to a single table subclass to produce
    the correct results, and overall will produce
    fewer WHERE criterion when dealing with
    single table inheritance joins.
    [ticket:2328]

  - [bug] __table_args__ can now be passed as
    an empty tuple as well as an empty dict.
    [ticket:2339].  Thanks to Fayaz Yusuf Khan
    for the patch.

  - [bug] Updated warning message when setting
    delete-orphan without delete to no longer
    refer to 0.6, as we never got around to
    upgrading this to an exception.  Ideally
    this might be better as an exception but
    it's not critical either way.  [ticket:2325]

  - [feature] polymorphic_on now accepts many
    new kinds of values:

      - standalone expressions that aren't
        otherwise mapped
      - column_property() objects
      - string names of any column_property()
        or attribute name of a mapped Column

    The docs include an example using
    the case() construct, which is likely to be
    a common constructed used here.
    [ticket:2345] and part of [ticket:2238]

    Standalone expressions in polymorphic_on
    propagate to single-table inheritance
    subclasses so that they are used in the
    WHERE /JOIN clause to limit rows to that
    subclass as is the usual behavior.

  - [feature] IdentitySet supports the - operator
    as the same as difference(), handy when dealing
    with Session.dirty etc. [ticket:2301]

  - [feature] Added new value for Column autoincrement
    called "ignore_fk", can be used to force autoincrement
    on a column that's still part of a ForeignKeyConstraint.
    New example in the relationship docs illustrates
    its use.

  - [bug] Fixed bug in get_history() when referring
    to a composite attribute that has no value;
    added coverage for get_history() regarding
    composites which is otherwise just a userland
    function.

- sql
   - [bug] related to [ticket:2316], made some
     adjustments to the change from [ticket:2261]
     regarding the "from" list on a select(). The
     _froms collection is no longer memoized, as this
     simplifies various use cases and removes the
     need for a "warning" if a column is attached
     to a table after it was already used in an
     expression - the select() construct will now
     always produce the correct expression.
     There's probably no real-world
     performance hit here; select() objects are
     almost always made ad-hoc, and systems that
     wish to optimize the re-use of a select()
     would be using the "compiled_cache" feature.
     A hit which would occur when calling select.bind
     has been reduced, but the vast majority
     of users shouldn't be using "bound metadata"
     anyway :).

   - [feature] The update() construct can now accommodate
     multiple tables in the WHERE clause, which will
     render an "UPDATE..FROM" construct, recognized by
     Postgresql and MSSQL.  When compiled on MySQL,
     will instead generate "UPDATE t1, t2, ..".  MySQL
     additionally can render against multiple tables in the
     SET clause, if Column objects are used as keys
     in the "values" parameter or generative method.
     [ticket:2166] [ticket:1944]

   - [feature] Added accessor to types called "python_type",
     returns the rudimentary Python type object
     for a particular TypeEngine instance, if known,
     else raises NotImplementedError.  [ticket:77]

   - [bug] further tweak to the fix from [ticket:2261],
     so that generative methods work a bit better
     off of cloned (this is almost a non-use case though).
     In particular this allows with_only_columns()
     to behave more consistently.   Added additional
     documentation to with_only_columns() to clarify
     expected behavior, which changed as a result
     of [ticket:2261].  [ticket:2319]

- engine
  - [bug] Fixed bug whereby transaction.rollback()
    would throw an error on an invalidated
    connection if the transaction were a
    two-phase or savepoint transaction.
    For plain transactions, rollback() is a no-op
    if the connection is invalidated, so while
    it wasn't 100% clear if it should be a no-op,
    at least now the interface is consistent.
    [ticket:2317]

- schema
  - [feature] Added new support for remote "schemas":
    - MetaData() accepts "schema" and "quote_schema"
      arguments, which will be applied to the same-named
      arguments of a Table
      or Sequence which leaves these at their default
      of ``None``.
    - Sequence accepts "quote_schema" argument
    - tometadata() for Table will use the "schema"
      of the incoming MetaData for the new Table
      if the schema argument is explicitly "None"
    - Added CreateSchema and DropSchema DDL
      constructs - these accept just the string
      name of a schema and a "quote" flag.
    - When using default "schema" with MetaData,
      ForeignKey will also assume the "default" schema
      when locating remote table.  This allows the "schema"
      argument on MetaData to be applied to any
      set of Table objects that otherwise don't have
      a "schema".
    - a "has_schema" method has been implemented
      on dialect, but only works on Postgresql so far.
    Courtesy Manlio Perillo, [ticket:1679]

  - [feature] The "extend_existing" flag on Table
    now allows for the reflection process to take
    effect for a Table object that's already been
    defined; when autoload=True and extend_existing=True
    are both set, the full set of columns will be
    reflected from the Table which will then
    *overwrite* those columns already present,
    rather than no activity occurring.  Columns that
    are present directly in the autoload run
    will be used as always, however.
    [ticket:1410]

  - [bug] Fixed bug whereby TypeDecorator would
    return a stale value for _type_affinity, when
    using a TypeDecorator that "switches" types,
    like the CHAR/UUID type.

  - [bug] Fixed bug whereby "order_by='foreign_key'"
    option to Inspector.get_table_names
    wasn't implementing the sort properly, replaced
    with the existing sort algorithm

  - [bug] the "name" of a column-level CHECK constraint,
    if present, is now rendered in the CREATE TABLE
    statement using "CONSTRAINT <name> CHECK <expression>".
    [ticket:2305]

- pyodbc
   - [bug] pyodbc-based dialects now parse the
     pyodbc accurately as far as observed
     pyodbc strings, including such gems
     as "py3-3.0.1-beta4" [ticket:2318]

- postgresql
   - [bug] Postgresql dialect memoizes that an ENUM of a
     particular name was processed
     during a create/drop sequence.  This allows
     a create/drop sequence to work without any
     calls to "checkfirst", and also means with
     "checkfirst" turned on it only needs to
     check for the ENUM once.  [ticket:2311]

   - [feature] Added create_type constructor argument
     to pg.ENUM.  When False, no CREATE/DROP or
     checking for the type will be performed as part
     of a table create/drop event; only the
     create()/drop)() methods called directly
     will do this.  Helps with Alembic "offline"
     scripts.

- mssql
  - [feature] lifted the restriction on SAVEPOINT
    for SQL Server.  All tests pass using it,
    it's not known if there are deeper issues
    however.   [ticket:822]

  - [bug] repaired the with_hint() feature which
    wasn't implemented correctly on MSSQL -
    usually used for the "WITH (NOLOCK)" hint
    (which you shouldn't be using anyway !
    use snapshot isolation instead :) )
    [ticket:2336]

  - [bug] use new pyodbc version detection for
    _need_decimal_fix option, [ticket:2318]

  - [bug] don't cast "table name" as NVARCHAR
    on SQL Server 2000.  Still mostly in the dark
    what incantations are needed to make PyODBC
    work fully with FreeTDS 0.91 here, however.
    [ticket:2343]

  - [bug] Decode incoming values when retrieving
    list of index names and the names of columns
    within those indexes.  [ticket:2269]

- mysql
  - [bug] Unicode adjustments allow latest pymysql
    (post 0.4) to pass 100% on Python 2.

- ext
   - [feature] Added an example to the hybrid docs
     of a "transformer" - a hybrid that returns a
     query-transforming callable in combination
     with a custom comparator.   Uses a new method
     on Query called with_transformation().  The use
     case here is fairly experimental, but only
     adds one line of code to Query.

   - [bug] the @compiles decorator raises an
     informative error message when no "default"
     compilation handler is present, rather
     than KeyError.

- examples
   - [bug] Fixed bug in history_meta.py example where
     the "unique" flag was not removed from a
     single-table-inheritance subclass which
     generates columns to put up onto the base.

0.7.3
=====
- general
   - Adjusted the "importlater" mechanism, which is
     used internally to resolve import cycles,
     such that the usage of __import__ is completed
     when the import of sqlalchemy or sqlalchemy.orm
     is done, thereby avoiding any usage of __import__
     after the application starts new threads,
     fixes [ticket:2279].  Also in 0.6.9.

- orm
   - Improved query.join() such that the "left" side
     can more flexibly be a non-ORM selectable,
     such as a subquery.   A selectable placed
     in select_from() will now be used as the left
     side, favored over implicit usage
     of a mapped entity.
     If the join still fails based on lack of
     foreign keys, the error message includes
     this detail.  Thanks to brianrhude
     on IRC for the test case.  [ticket:2298]

   - Added after_soft_rollback() Session event.  This
     event fires unconditionally whenever rollback()
     is called, regardless of if an actual DBAPI
     level rollback occurred.  This event
     is specifically designed to allow operations
     with the Session to proceed after a rollback
     when the Session.is_active is True.
     [ticket:2241]

  - added "adapt_on_names" boolean flag to orm.aliased()
    construct.  Allows an aliased() construct
    to link the ORM entity to a selectable that contains
    aggregates or other derived forms of a particular
    attribute, provided the name is the same as that
    of the entity mapped column.

  - Added new flag expire_on_flush=False to column_property(),
    marks those properties that would otherwise be considered
    to be "readonly", i.e. derived from SQL expressions,
    to retain their value after a flush has occurred, including
    if the parent object itself was involved in an update.

  - Enhanced the instrumentation in the ORM to support
    Py3K's new argument style of "required kw arguments",
    i.e. fn(a, b, *, c, d), fn(a, b, *args, c, d).
    Argument signatures of mapped object's __init__
    method will be preserved, including required kw rules.
    [ticket:2237]

  - Fixed bug in unit of work whereby detection of
    "cycles" among classes in highly interlinked patterns
    would not produce a deterministic
    result; thereby sometimes missing some nodes that
    should be considered cycles and causing further
    issues down the road.  Note this bug is in 0.6
    also; not backported at the moment.
    [ticket:2282]

  - Fixed a variety of synonym()-related regressions
    from 0.6:
        - making a synonym against a synonym now works.
        - synonyms made against a relationship() can
          be passed to query.join(), options sent
          to query.options(), passed by name
          to query.with_parent().

  - Fixed bug whereby mapper.order_by attribute would
    be ignored in the "inner" query within a
    subquery eager load.  [ticket:2287].
    Also in 0.6.9.

  - Identity map .discard() uses dict.pop(,None)
    internally instead of "del" to avoid KeyError/warning
    during a non-determinate gc teardown [ticket:2267]

  - Fixed regression in new composite rewrite where
    deferred=True option failed due to missing
    import [ticket:2253]

  - Reinstated "comparator_factory" argument to
    composite(), removed when 0.7 was released.
    [ticket:2248]

  - Fixed bug in query.join() which would occur
    in a complex multiple-overlapping path scenario,
    where the same table could be joined to
    twice.  Thanks *much* to Dave Vitek
    for the excellent fix here.  [ticket:2247]

  - Query will convert an OFFSET of zero when
    slicing into None, so that needless OFFSET
    clauses are not invoked.

  - Repaired edge case where mapper would fail
    to fully update internal state when a relationship
    on a new mapper would establish a backref on the
    first mapper.

  - Fixed bug whereby if __eq__() was
    redefined, a relationship many-to-one lazyload
    would hit the __eq__() and fail.  [ticket:2260]
    Does not apply to 0.6.9.

  - Calling class_mapper() and passing in an object
    that is not a "type" (i.e. a class that could
    potentially be mapped) now raises an informative
    ArgumentError, rather than UnmappedClassError.
    [ticket:2196]

  - New event hook, MapperEvents.after_configured().
    Called after a configure() step has completed and
    mappers were in fact affected.   Theoretically this
    event is called once per application, unless new mappings
    are constructed after existing ones have been used
    already.

  - When an open Session is garbage collected, the objects
    within it which remain are considered detached again
    when they are add()-ed to a new Session.
    This is accomplished by an extra check that the previous
    "session_key" doesn't actually exist among the pool
    of Sessions.  [ticket:2281]

  - New declarative features:
        - __declare_last__() method, establishes an event
        listener for the class method that will be called
        when mappers are completed with the final "configure"
        step.
        - __abstract__ flag.   The class will not be mapped
        at all when this flag is present on the class.
        - New helper classes ConcreteBase, AbstractConcreteBase.
        Allow concrete mappings using declarative which automatically
        set up the "polymorphic_union" when the "configure"
        mapper step is invoked.
        - The mapper itself has semi-private methods that allow
        the "with_polymorphic" selectable to be assigned
        to the mapper after it has already been configured.
        [ticket:2239]

   - Declarative will warn when a subclass' base uses
     @declared_attr for a regular column - this attribute
     does not propagate to subclasses. [ticket:2283]

   - The integer "id" used to link a mapped instance with
     its owning Session is now generated by a sequence
     generation function rather than id(Session), to
     eliminate the possibility of recycled id() values
     causing an incorrect result, no need to check that
     object actually in the session.  [ticket:2280]

-sql
  - Behavioral improvement: empty
    conjunctions such as and_() and or_() will be
    flattened in the context of an enclosing conjunction,
    i.e. and_(x, or_()) will produce 'X' and not 'X AND
    ()'. [ticket:2257].

  - Fixed bug regarding calculation of "from" list
    for a select() element.  The "from" calc is now
    delayed, so that if the construct uses a Column
    object that is not yet attached to a Table,
    but is later associated with a Table, it generates
    SQL using the table as a FROM.   This change
    impacted fairly deeply the mechanics of how
    the FROM list as well as the "correlates" collection
    is calculated, as some "clause adaption" schemes
    (these are used very heavily in the ORM)
    were relying upon the fact that the "froms"
    collection would typically be cached before the
    adaption completed.   The rework allows it
    such that the "froms" collection can be cleared
    and re-generated at any time.  [ticket:2261]

  - Fixed bug whereby with_only_columns() method of
    Select would fail if a selectable were passed.
    [ticket:2270].  Also in 0.6.9.

- schema
  - Modified Column.copy() to use _constructor(),
    which defaults to self.__class__, in order to
    create the new object.  This allows easier support
    of subclassing Column.  [ticket:2284]

  - Added a slightly nicer __repr__() to SchemaItem
    classes.  Note the repr here can't fully support
    the "repr is the constructor" idea since schema
    items can be very deeply nested/cyclical, have
    late initialization of some things, etc.
    [ticket:2223]

- engine
  - The recreate() method in all pool classes uses
    self.__class__ to get at the type of pool
    to produce, in the case of subclassing.  Note
    there's no usual need to subclass pools.
    [ticket:2254]

  - Improvement to multi-param statement logging,
    long lists of bound parameter sets will be
    compressed with an informative indicator
    of the compression taking place.  Exception
    messages use the same improved formatting.
    [ticket:2243]

  - Added optional "sa_pool_key" argument to
    pool.manage(dbapi).connect() so that serialization
    of args is not necessary.

  - The entry point resolution supported by
    create_engine() now supports resolution of
    individual DBAPI drivers on top of a built-in
    or entry point-resolved dialect, using the
    standard '+' notation - it's converted to
    a '.' before being resolved as an entry
    point.  [ticket:2286]

  - Added an exception catch + warning for the
    "return unicode detection" step within connect,
    allows databases that crash on NVARCHAR to
    continue initializing, assuming no NVARCHAR
    type implemented.  [ticket:2299]

- types
  - Extra keyword arguments to the base Float
    type beyond "precision" and "asdecimal" are ignored;
    added a deprecation warning here and additional
    docs, related to [ticket:2258]

- sqlite
  - Ensured that the same ValueError is raised for
    illegal date/time/datetime string parsed from
    the database regardless of whether C
    extensions are in use or not.

- postgresql
  - Added "postgresql_using" argument to Index(), produces
    USING clause to specify index implementation for
    PG.  [ticket:2290].  Thanks to Ryan P. Kelly for
    the patch.

  - Added client_encoding parameter to create_engine()
    when the postgresql+psycopg2 dialect is used;
    calls the psycopg2 set_client_encoding() method
    with the value upon connect.  [ticket:1839]

  - Fixed bug related to [ticket:2141] whereby the
    same modified index behavior in PG 9 affected
    primary key reflection on a renamed column.
    [ticket:2291].  Also in 0.6.9.

  - Reflection functions for Table, Sequence no longer
    case insensitive.  Names can be differ only in case
    and will be correctly distinguished.  [ticket:2256]

  - Use an atomic counter as the "random number"
    source for server side cursor names;
    conflicts have been reported in rare cases.

  - Narrowed the assumption made when reflecting
    a foreign-key referenced table with schema in
    the current search path; an explicit schema will
    be applied to the referenced table only if
    it actually matches that of the referencing table,
    which also has an explicit schema.   Previously
    it was assumed that "current" schema was synonymous
    with the full search_path.  [ticket:2249]

- mysql
  - a CREATE TABLE will put the COLLATE option
    after CHARSET, which appears to be part of
    MySQL's arbitrary rules regarding if it will actually
    work or not.  [ticket:2225]  Also in 0.6.9.

  - Added mysql_length parameter to Index construct,
    specifies "length" for indexes.  [ticket:2293]

- mssql
  - Changes to attempt support of FreeTDS 0.91 with
    Pyodbc.  This includes that string binds are sent as
    Python unicode objects when FreeTDS 0.91 is detected,
    and a CAST(? AS NVARCHAR) is used when we detect
    for a table.   However, I'd continue
    to characterize Pyodbc + FreeTDS 0.91 behavior as
    pretty crappy, there are still many queries such
    as used in reflection which cause a core dump on
    Linux, and it is not really usable at all
    on OSX, MemoryErrors abound and just plain broken
    unicode support.   [ticket:2273]

  - The behavior of =/!= when comparing a scalar select
    to a value will no longer produce IN/NOT IN as of 0.8;
    this behavior is a little too heavy handed (use in_() if
    you want to emit IN) and now emits a deprecation warning.
    To get the 0.8 behavior immediately and remove the warning,
    a compiler recipe is given at
    http://www.sqlalchemy.org/docs/07/dialects/mssql.html#scalar-select-comparisons
    to override the behavior of visit_binary().
    [ticket:2277]

  - "0" is accepted as an argument for limit() which
    will produce "TOP 0". [ticket:2222]

- oracle
  - Fixed ReturningResultProxy for zxjdbc dialect.
    [ticket:2272].  Regression from 0.6.

  - The String type now generates VARCHAR2 on Oracle
    which is recommended as the default VARCHAR.
    Added an explicit VARCHAR2 and NVARCHAR2 to the Oracle
    dialect as well.   Using NVARCHAR still generates
    "NVARCHAR2" - there is no "NVARCHAR" on Oracle -
    this remains a slight breakage of the "uppercase types
    always give exactly that" policy.  VARCHAR still
    generates "VARCHAR", keeping with the policy.   If
    Oracle were to ever define "VARCHAR" as something
    different as they claim (IMHO this will never happen),
    the type would be available.  [ticket:2252]

- ext
  - SQLSoup will not be included in version 0.8
    of SQLAlchemy; while useful, we would like to
    keep SQLAlchemy itself focused on one ORM
    usage paradigm.  SQLSoup will hopefully
    soon be superseded by a third party
    project.  [ticket:2262]

  - Added local_attr, remote_attr, attr accessors
    to AssociationProxy, providing quick access
    to the proxied attributes at the class
    level. [ticket:2236]

  - Changed the update() method on association proxy
    dictionary to use a duck typing approach, i.e.
    checks for "keys", to discern between update({})
    and update((a, b)).   Previously, passing a
    dictionary that had tuples as keys would be misinterpreted
    as a sequence. [ticket:2275]

- examples
  - Adjusted dictlike-polymorphic.py example
    to apply the CAST such that it works on
    PG, other databases.  [ticket:2266]
    Also in 0.6.9.

0.7.2
=====
- orm
  - Feature enhancement: joined and subquery
    loading will now traverse already-present related
    objects and collections in search of unpopulated
    attributes throughout the scope of the eager load
    being defined, so that the eager loading that is
    specified via mappings or query options
    unconditionally takes place for the full depth,
    populating whatever is not already populated.
    Previously, this traversal would stop if a related
    object or collection were already present leading
    to inconsistent behavior (though would save on
    loads/cycles for an already-loaded graph). For a
    subqueryload, this means that the additional
    SELECT statements emitted by subqueryload will
    invoke unconditionally, no matter how much of the
    existing graph is already present (hence the
    controversy). The previous behavior of "stopping"
    is still in effect when a query is the result of
    an attribute-initiated lazyload, as otherwise an
    "N+1" style of collection iteration can become
    needlessly expensive when the same related object
    is encountered repeatedly. There's also an
    as-yet-not-public generative Query method
    _with_invoke_all_eagers()
    which selects old/new behavior [ticket:2213]

  - A rework of "replacement traversal" within
    the ORM as it alters selectables to be against
    aliases of things (i.e. clause adaption) includes
    a fix for multiply-nested any()/has() constructs
    against a joined table structure.  [ticket:2195]

  - Fixed bug where query.join() + aliased=True
    from a joined-inh structure to itself on
    relationship() with join condition on the child
    table would convert the lead entity into the
    joined one inappropriately.  [ticket:2234]
    Also in 0.6.9.

  - Fixed regression from 0.6 where Session.add()
    against an object which contained None in a
    collection would raise an internal exception.
    Reverted this to 0.6's behavior which is to
    accept the None but obviously nothing is
    persisted.  Ideally, collections with None
    present or on append() should at least emit a
    warning, which is being considered for 0.8.
    [ticket:2205]

  - Load of a deferred() attribute on an object
    where row can't be located raises
    ObjectDeletedError instead of failing later
    on; improved the message in ObjectDeletedError
    to include other conditions besides a simple
    "delete". [ticket:2191]

  - Fixed regression from 0.6 where a get history
    operation on some relationship() based attributes
    would fail when a lazyload would emit; this could
    trigger within a flush() under certain conditions.
    [ticket:2224]  Thanks to the user who submitted
    the great test for this.

  - Fixed bug apparent only in Python 3 whereby
    sorting of persistent + pending objects during
    flush would produce an illegal comparison,
    if the persistent object primary key
    is not a single integer.  [ticket:2228]
    Also in 0.6.9

  - Fixed bug whereby the source clause
    used by query.join() would be inconsistent
    if against a column expression that combined
    multiple entities together.  [ticket:2197]
    Also in 0.6.9

  - Fixed bug whereby if a mapped class
    redefined __hash__() or __eq__() to something
    non-standard, which is a supported use case
    as SQLA should never consult these,
    the methods would be consulted if the class
    was part of a "composite" (i.e. non-single-entity)
    result set.  [ticket:2215]
    Also in 0.6.9.

  - Added public attribute ".validators" to
    Mapper, an immutable dictionary view of
    all attributes that have been decorated
    with the @validates decorator.
    [ticket:2240] courtesy Stefano Fontanelli

  - Fixed subtle bug that caused SQL to blow
    up if: column_property() against subquery +
    joinedload + LIMIT + order by the column
    property() occurred.  [ticket:2188].
    Also in 0.6.9

  - The join condition produced by with_parent
    as well as when using a "dynamic" relationship
    against a parent will generate unique
    bindparams, rather than incorrectly repeating
    the same bindparam.  [ticket:2207].
    Also in 0.6.9.

  - Added the same "columns-only" check to
    mapper.polymorphic_on as used when
    receiving user arguments to
    relationship.order_by, foreign_keys,
    remote_side, etc.

  - Fixed bug whereby comparison of column
    expression to a Query() would not call
    as_scalar() on the underlying SELECT
    statement to produce a scalar subquery,
    in the way that occurs if you called
    it on Query().subquery(). [ticket:2190]

  - Fixed declarative bug where a class inheriting
    from a superclass of the same name would fail
    due to an unnecessary lookup of the name
    in the _decl_class_registry. [ticket:2194]

  - Repaired the "no statement condition"
    assertion in Query which would attempt
    to raise if a generative method were called
    after from_statement() were called.
    [ticket:2199].  Also in 0.6.9.

- sql
  - Fixed two subtle bugs involving column
    correspondence in a selectable,
    one with the same labeled subquery repeated, the other
    when the label has been "grouped" and
    loses itself.  Affects [ticket:2188].

- schema
  - New feature: with_variant() method on
    all types.  Produces an instance of Variant(),
    a special TypeDecorator which will select
    the usage of a different type based on the
    dialect in use. [ticket:2187]

  - Added an informative error message when
    ForeignKeyConstraint refers to a column name in
    the parent that is not found.  Also in 0.6.9.

  - Fixed bug whereby adaptation of old append_ddl_listener()
    function was passing unexpected **kw through
    to the Table event.   Table gets no kws, the MetaData
    event in 0.6 would get "tables=somecollection",
    this behavior is preserved.  [ticket:2206]

  - Fixed bug where "autoincrement" detection on
    Table would fail if the type had no "affinity"
    value, in particular this would occur when using
    the UUID example on the site that uses TypeEngine
    as the "impl".

  - Added an improved repr() to TypeEngine objects
    that will only display constructor args which
    are positional or kwargs that deviate
    from the default.  [ticket:2209]

- engine
  - Context manager provided by Connection.begin()
    will issue rollback() if the commit() fails,
    not just if an exception occurs.

  - Use urllib.parse_qsl() in Python 2.6 and above,
    no deprecation warning about cgi.parse_qsl()
    [ticket:1682]

  - Added mixin class sqlalchemy.ext.DontWrapMixin.
    User-defined exceptions of this type are never
    wrapped in StatementException when they
    occur in the context of a statement
    execution.

  - StatementException wrapping will display the
    original exception class in the message.

  - Failures on connect which raise dbapi.Error
    will forward the error to dialect.is_disconnect()
    and set the "connection_invalidated" flag if
    the dialect knows this to be a potentially
    "retryable" condition.  Only Oracle ORA-01033
    implemented for now.  [ticket:2201]

- sqlite
  - SQLite dialect no longer strips quotes
    off of reflected default value, allowing
    a round trip CREATE TABLE to work.
    This is consistent with other dialects
    that also maintain the exact form of
    the default.  [ticket:2189]

- postgresql
  - Added new "postgresql_ops" argument to
    Index, allows specification of PostgreSQL
    operator classes for indexed columns.
    [ticket:2198]  Courtesy Filip Zyzniewski.

- mysql
  - Fixed OurSQL dialect to use ansi-neutral
    quote symbol "'" for XA commands instead
    of '"'.  [ticket:2186].  Also in 0.6.9.

- mssql
  - Adjusted the pyodbc dialect such that bound
    values are passed as bytes and not unicode
    if the "Easysoft" unix drivers are detected.
    This is the same behavior as occurs with
    FreeTDS.  Easysoft appears to segfault
    if Python unicodes are passed under
    certain circumstances.

- oracle
  - Added ORA-00028 to disconnect codes, use
    cx_oracle _Error.code to get at the code,
    [ticket:2200].  Also in 0.6.9.

  - Added ORA-01033 to disconnect codes, which
    can be caught during a connection
    event.  [ticket:2201]

  - repaired the oracle.RAW type which did not
    generate the correct DDL.  [ticket:2220]
    Also in 0.6.9.

  - added CURRENT to reserved word list.
    [ticket:2212] Also in 0.6.9.

-ext
  - Fixed bug in the mutable extension whereby
    if the same type were used twice in one
    mapping, the attributes beyond the first
    would not get instrumented.

  - Fixed bug in the mutable extension whereby
    if None or a non-corresponding type were set,
    an error would be raised.  None is now accepted
    which assigns None to all attributes,
    illegal values raise ValueError.

- examples
  - Repaired the examples/versioning test runner
    to not rely upon SQLAlchemy test libs,
    nosetests must be run from within
    examples/versioning to get around setup.cfg
    breaking it.

  - Tweak to examples/versioning to pick the
    correct foreign key in a multi-level
    inheritance situation.

  - Fixed the attribute shard example to check
    for bind param callable correctly in 0.7
    style.

0.7.1
=====
- general
  - Added a workaround for Python bug 7511 where
    failure of C extension build does not
    raise an appropriate exception on Windows 64
    bit + VC express [ticket:2184]

- orm
  - "delete-orphan" cascade is now allowed on
    self-referential relationships - this since
    SQLA 0.7 no longer enforces "parent with no
    child" at the ORM level; this check is left
    up to foreign key nullability.
    Related to [ticket:1912]

  - Repaired new "mutable" extension to propagate
    events to subclasses correctly; don't
    create multiple event listeners for
    subclasses either.  [ticket:2180]

  - Modify the text of the message which occurs
    when the "identity" key isn't detected on
    flush, to include the common cause that
    the Column isn't set up to detect
    auto-increment correctly; [ticket:2170].
    Also in 0.6.8.

  - Fixed bug where transaction-level "deleted"
    collection wouldn't be cleared of expunged
    states, raising an error if they later
    became transient [ticket:2182].
    Also in 0.6.8.

- sql
  - Fixed bug whereby metadata.reflect(bind)
    would close a Connection passed as a
    bind argument.  Regression from 0.6.

  - Streamlined the process by which a Select
    determines what's in it's '.c' collection.
    Behaves identically, except that a
    raw ClauseList() passed to select([])
    (which is not a documented case anyway) will
    now be expanded into its individual column
    elements instead of being ignored.

- engine
  - Deprecate schema/SQL-oriented methods on
    Connection/Engine that were never well known
    and are redundant:  reflecttable(), create(),
    drop(), text(), engine.func

  - Adjusted the __contains__() method of
    a RowProxy result row such that no exception
    throw is generated internally;
    NoSuchColumnError() also will generate its
    message regardless of whether or not the column
    construct can be coerced to a string.
    [ticket:2178].  Also in 0.6.8.

- sqlite
  - Accept None from cursor.fetchone() when
    "PRAGMA read_uncommitted" is called to determine
    current isolation mode at connect time and
    default to SERIALIZABLE; this to support SQLite
    versions pre-3.3.0 that did not have this
    feature.  [ticket:2173]

- postgresql
  - Some unit test fixes regarding numeric arrays,
    MATCH operator.   A potential floating-point
    inaccuracy issue was fixed, and certain tests
    of the MATCH operator only execute within an
    EN-oriented locale for now.  [ticket:2175].
    Also in 0.6.8.

- mysql
  - Unit tests pass 100% on MySQL installed
    on windows.

  - Removed the "adjust casing" step that would
    fail when reflecting a table on MySQL
    on windows with a mixed case name.  After some
    experimenting with a windows MySQL server, it's
    been determined that this step wasn't really
    helping the situation much; MySQL does not return
    FK names with proper casing on non-windows
    platforms either, and removing the step at
    least allows the reflection to act more like
    it does on other OSes.   A warning here
    has been considered but its difficult to
    determine under what conditions such a warning
    can be raised, so punted on that for now -
    added some docs instead. [ticket:2181]

  - supports_sane_rowcount will be set to False
    if using MySQLdb and the DBAPI doesn't provide
    the constants.CLIENT module.

0.7.0
=======
- This section documents those changes from 0.7b4
  to 0.7.0.  For an overview of what's new in
  SQLAlchemy 0.7, see
  http://www.sqlalchemy.org/trac/wiki/07Migration

- orm
  - Fixed regression introduced in 0.7b4 (!) whereby
    query.options(someoption("nonexistent name")) would
    fail to raise an error.  Also added additional
    error catching for cases where the option would
    try to build off a column-based element, further
    fixed up some of the error messages tailored
    in [ticket:2069]

  - query.count() emits "count(*)" instead of
    "count(1)".  [ticket:2162]

  - Fine tuning of Query clause adaptation when
    from_self(), union(), or other "select from
    myself" operation, such that plain SQL expression
    elements added to filter(), order_by() etc.
    which are present in the nested "from myself"
    query *will* be adapted in the same way an ORM
    expression element will, since these
    elements are otherwise not easily accessible.
    [ticket:2155]

  - Fixed bug where determination of "self referential"
    relationship would fail with no workaround
    for joined-inh subclass related to itself,
    or joined-inh subclass related to a subclass
    of that with no cols in the sub-sub class
    in the join condition.  [ticket:2149]
    Also in 0.6.8.

  - mapper() will ignore non-configured foreign keys
    to unrelated tables when determining inherit
    condition between parent and child class,
    but will raise as usual for unresolved
    columns and table names regarding the inherited
    table.  This is an enhanced generalization of
    behavior that was already applied to declarative
    previously.  [ticket:2153]   0.6.8 has a more
    conservative version of this which doesn't
    fundamentally alter how join conditions
    are determined.

  - It is an error to call query.get() when the
    given entity is not a single, full class
    entity or mapper (i.e. a column).  This is
    a deprecation warning in 0.6.8.
    [ticket:2144]

  - Fixed a potential KeyError which under some
    circumstances could occur with the identity
    map, part of [ticket:2148]

  - added Query.with_session() method, switches
    Query to use a different session.

  - horizontal shard query should use execution
    options per connection as per [ticket:2131]

  - a non_primary mapper will inherit the _identity_class
    of the primary mapper.  This so that a non_primary
    established against a class that's normally in an
    inheritance mapping will produce results that are
    identity-map compatible with that of the primary
    mapper [ticket:2151] (also in 0.6.8)

  - Fixed the error message emitted for "can't
    execute syncrule for destination column 'q';
    mapper 'X' does not map this column" to
    reference the correct mapper.  [ticket:2163].
    Also in 0.6.8.

  - polymorphic_union() gets a "cast_nulls" option,
    disables the usage of CAST when it renders
    the labeled NULL columns.  [ticket:1502]

  - polymorphic_union() renders the columns in their
    original table order, as according to the first
    table/selectable in the list of polymorphic
    unions in which they appear.  (which is itself
    an unordered mapping unless you pass an OrderedDict).

  - Fixed bug whereby mapper mapped to an anonymous
    alias would fail if logging were used, due to
    unescaped % sign in the alias name.  [ticket:2171]
    Also in 0.6.8.

- sql
  - Fixed bug whereby nesting a label of a select()
    with another label in it would produce incorrect
    exported columns.   Among other things this would
    break an ORM column_property() mapping against
    another column_property().  [ticket:2167].
    Also in 0.6.8

  - Changed the handling in determination of join
    conditions such that foreign key errors are
    only considered between the two given tables.
    That is, t1.join(t2) will report FK errors
    that involve 't1' or 't2', but anything
    involving 't3' will be skipped.   This affects
    join(), as well as ORM relationship and
    inherit condition logic.

  - Some improvements to error handling inside
    of the execute procedure to ensure auto-close
    connections are really closed when very
    unusual DBAPI errors occur.

  - metadata.reflect() and reflection.Inspector()
    had some reliance on GC to close connections
    which were internally procured, fixed this.

  - Added explicit check for when Column .name
    is assigned as blank string [ticket:2140]

  - Fixed bug whereby if FetchedValue was passed
    to column server_onupdate, it would not
    have its parent "column" assigned, added
    test coverage for all column default assignment
    patterns.  [ticket:2147]  also in 0.6.8

- postgresql
  - Fixed the psycopg2_version parsing in the
    psycopg2 dialect.

  - Fixed bug affecting PG 9 whereby index reflection
    would fail if against a column whose name
    had changed.  [ticket:2141].  Also in 0.6.8.

- mssql
  - Fixed bug in MSSQL dialect whereby the aliasing
    applied to a schema-qualified table would leak
    into enclosing select statements [ticket:2169].
    Also in 0.6.8.

- documentation
  - Removed the usage of the "collections.MutableMapping"
    abc from the ext.mutable docs as it was being used
    incorrectly and makes the example more difficult
    to understand in any case.  [ticket:2152]

- examples
  - removed the ancient "polymorphic association"
    examples and replaced with an updated set of
    examples that use declarative mixins,
    "generic_associations".   Each presents an alternative
    table layout.

- ext
  - Fixed bugs in sqlalchemy.ext.mutable extension where
    `None` was not appropriately handled, replacement
    events were not appropriately handled.
    [ticket:2143]

0.7.0b4
=======
- general
  - Changes to the format of CHANGES, this file.
    The format changes have been applied to
    the 0.7 releases.

    - The "-declarative" changes will now be listed
      directly under the "-orm" section, as these
      are closely related.

    - The 0.5 series changes have been moved to
      the file CHANGES_PRE_06 which replaces
      CHANGES_PRE_05.

    - The changelog for 0.6.7 and subsequent within
      the 0.6 series is now listed only in the
      CHANGES file within the 0.6 branch.
      In the 0.7 CHANGES file (i.e. this file), all the
      0.6 changes are listed inline within the 0.7
      section in which they were also applied
      (since all 0.6 changes are in 0.7 as well).
      Changes that apply to an 0.6 version here
      are noted as are if any differences in
      implementation/behavior are present.

- orm
  - Some fixes to "evaulate" and "fetch" evaluation
    when query.update(), query.delete() are called.
    The retrieval of records is done after autoflush
    in all cases, and before update/delete is
    emitted, guarding against unflushed data present
    as well as expired objects failing during
    the evaluation.  [ticket:2122]

  - Reworded the exception raised when a flush
    is attempted of a subclass that is not polymorphic
    against the supertype.  [ticket:2063]

  - Still more wording adjustments when a query option
    can't find the target entity.  Explain that the
    path must be from one of the root entities.

  - Some fixes to the state handling regarding
    backrefs, typically when autoflush=False, where
    the back-referenced collection wouldn't
    properly handle add/removes with no net
    change.  Thanks to Richard Murri for the
    test case + patch.  [ticket:2123]
    (also in 0.6.7).

  - Added checks inside the UOW to detect the unusual
    condition of being asked to UPDATE or DELETE
    on a primary key value that contains NULL
    in it.  [ticket:2127]

  - Some refinements to attribute history.  More
    changes are pending possibly in 0.8, but
    for now history has been modified such that
    scalar history doesn't have a "side effect"
    of populating None for a non-present value.
    This allows a slightly better ability to
    distinguish between a None set and no actual
    change, affects [ticket:2127] as well.

  - a "having" clause would be copied from the
    inside to the outside query if from_self()
    were used; in particular this would break
    an 0.7 style count() query [ticket:2130].
    (also in 0.6.7)

  - the Query.execution_options() method now passes
    those options to the Connection rather than
    the SELECT statement, so that all available
    options including isolation level and
    compiled cache may be used.  [ticket:2131]

- sql
  - The "compiled_cache" execution option now raises
    an error when passed to a SELECT statement
    rather than a Connection.  Previously it was
    being ignored entirely.   We may look into
    having this option work on a per-statement
    level at some point. [ticket:2131]

  - Restored the "catchall" constructor on the base
    TypeEngine class, with a deprecation warning.
    This so that code which does something like
    Integer(11) still succeeds.

  - Fixed regression whereby MetaData() coming
    back from unpickling did not keep track of
    new things it keeps track of now, i.e.
    collection of Sequence objects, list
    of schema names.  [ticket:2104]

  - The limit/offset keywords to select() as well
    as the value passed to select.limit()/offset()
    will be coerced to integer.  [ticket:2116]
    (also in 0.6.7)

  - fixed bug where "from" clause gathering from an
    over() clause would be an itertools.chain() and
    not a list, causing "can only concatenate list"
    TypeError when combined with other clauses.

  - Fixed incorrect usage of "," in over() clause
    being placed between the "partition" and "order by"
    clauses.  [ticket:2134]

  - Before/after attach events for PrimaryKeyConstraint
    now function, tests added for before/after events
    on all constraint types.  [ticket:2105]

  - Added explicit true()/false() constructs to expression
    lib - coercion rules will intercept "False"/"True"
    into these constructs.  In 0.6, the constructs were
    typically converted straight to string, which was
    no longer accepted in 0.7.  [ticket:2117]

- engine
  - The C extension is now enabled by default on CPython
    2.x with a fallback to pure python if it fails to
    compile.  [ticket:2129]

- schema
  - The 'useexisting' flag on Table has been superceded
    by a new pair of flags 'keep_existing' and
    'extend_existing'.   'extend_existing' is equivalent
    to 'useexisting' - the existing Table is returned,
    and additional constructor elements are added.
    With 'keep_existing', the existing Table is returned,
    but additional constructor elements are not added -
    these elements are only applied when the Table
    is newly created.   [ticket:2109]

- types
  - REAL has been added to the core types.  Supported
    by Postgresql, SQL Server, MySQL, SQLite.  Note
    that the SQL Server and MySQL versions, which
    add extra arguments, are also still available
    from those dialects.  [ticket:2081]

-event
  - Added @event.listens_for() decorator, given
    target + event name, applies the decorated
    function as a listener.  [ticket:2106]

- pool
  - AssertionPool now stores the traceback indicating
    where the currently checked out connection was
    acquired; this traceback is reported within
    the assertion raised upon a second concurrent
    checkout; courtesy Gunnlaugur Briem
    [ticket:2103]

  - The "pool.manage" feature doesn't use pickle
    anymore to hash the arguments for each pool.

- sqlite
  - Fixed bug where reflection of foreign key
    created as "REFERENCES <tablename>" without
    col name would fail.  [ticket:2115]
    (also in 0.6.7)

- postgresql
  - Psycopg2 for Python 3 is now supported.

  - Fixed support for precision numerics when using
    pg8000. [ticket:2132]

- oracle
  - Using column names that would require quotes
    for the column itself or for a name-generated
    bind parameter, such as names with special
    characters, underscores, non-ascii characters,
    now properly translate bind parameter keys when
    talking to cx_oracle.  [ticket:2100]  (Also
    in 0.6.7)

  - Oracle dialect adds use_binds_for_limits=False
    create_engine() flag, will render the LIMIT/OFFSET
    values inline instead of as binds, reported to
    modify the execution plan used by Oracle.
    [ticket:2116] (Also in 0.6.7)

- documentation
  - Documented SQLite DATE/TIME/DATETIME types.
    [ticket:2029] (also in 0.6.7)

  - Fixed mutable extension docs to show the
    correct type-association methods.
    [ticket:2118]

0.7.0b3
=======
- general
  - Lots of fixes to unit tests when run under Pypy
    (courtesy Alex Gaynor).

- orm
  - Changed the underlying approach to query.count().
    query.count() is now in all cases exactly:

        query.
            from_self(func.count(literal_column('1'))).
            scalar()

    That is, "select count(1) from (<full query>)".
    This produces a subquery in all cases, but
    vastly simplifies all the guessing count()
    tried to do previously, which would still
    fail in many scenarios particularly when
    joined table inheritance and other joins
    were involved.  If the subquery produced
    for an otherwise very simple count is really
    an issue, use query(func.count()) as an
    optimization.  [ticket:2093]

  - some changes to the identity map regarding
    rare weakref callbacks during iterations.
    The mutex has been removed as it apparently
    can cause a reentrant (i.e. in one thread) deadlock,
    perhaps when gc collects objects at the point of
    iteration in order to gain more memory.  It is hoped
    that "dictionary changed during iteration" will
    be exceedingly rare as iteration methods internally
    acquire the full list of objects in a single values()
    call. Note 0.6.7 has a more conservative fix here
    which still keeps the mutex in place. [ticket:2087]

  - A tweak to the unit of work causes it to order
    the flush along relationship() dependencies even if
    the given objects don't have any inter-attribute
    references in memory, which was the behavior in
    0.5 and earlier, so a flush of Parent/Child with
    only foreign key/primary key set will succeed.
    This while still maintaining 0.6 and above's not
    generating a ton of useless internal dependency
    structures within the flush that don't correspond
    to state actually within the current flush.
    [ticket:2082]

  - Improvements to the error messages emitted when
    querying against column-only entities in conjunction
    with (typically incorrectly) using loader options,
    where the parent entity is not fully present.
    [ticket:2069]

  - Fixed bug in query.options() whereby a path
    applied to a lazyload using string keys could
    overlap a same named attribute on the wrong
    entity.  Note 0.6.7 has a more conservative fix
    to this.  [ticket:2098]

- declarative
  - Arguments in __mapper_args__ that aren't "hashable"
    aren't mistaken for always-hashable, possibly-column
    arguments.  [ticket:2091] (also in 0.6.7)

- sql
  - Added a fully descriptive error message for the
    case where Column is subclassed and _make_proxy()
    fails to make a copy due to TypeError on the
    constructor.   The method _constructor should
    be implemented in this case.

  - Added new event "column_reflect" for Table objects.
    Receives the info dictionary about a Column before
    the object is generated within reflection, and allows
    modification to the dictionary for control over
    most aspects of the resulting Column including
    key, name, type, info dictionary.  [ticket:2095]

  - To help with the "column_reflect" event being used
    with specific Table objects instead of all instances
    of Table, listeners can be added to a Table object
    inline with its construction using a new argument
    "listeners", a list of tuples of the form
    (<eventname>, <fn>), which are applied to the Table
    before the reflection process begins.

  - Added new generic function "next_value()", accepts
    a Sequence object as its argument and renders the
    appropriate "next value" generation string on the
    target platform, if supported.  Also provides
    ".next_value()" method on Sequence itself.
    [ticket:2085]

  - func.next_value() or other SQL expression can
    be embedded directly into an insert() construct,
    and if implicit or explicit "returning" is used
    in conjunction with a primary key column,
    the newly generated value will be present in
    result.inserted_primary_key. [ticket:2084]

  - Added accessors to ResultProxy "returns_rows",
    "is_insert" [ticket:2089] (also in 0.6.7)

- engine
  - Fixed AssertionPool regression bug.  [ticket:2097]

  - Changed exception raised to ArgumentError when an
    invalid dialect is specified. [ticket:2060]

- postgresql
  - Added RESERVED_WORDS for postgresql dialect. [ticket:2092]
    (also in 0.6.7)

  - Fixed the BIT type to allow a "length" parameter, "varying"
    parameter.  Reflection also fixed.  [ticket:2073]
    (also in 0.6.7)

- mssql
  - Rewrote the query used to get the definition of a view,
    typically when using the Inspector interface, to
    use sys.sql_modules instead of the information schema,
    thereby allowing views definitions longer than 4000
    characters to be fully returned.  [ticket:2071]
    (also in 0.6.7)

- firebird
  - The "implicit_returning" flag on create_engine() is
    honored if set to False.  [ticket:2083] (also in 0.6.7)

- informix

  - Added RESERVED_WORDS informix dialect. [ticket:2092]
    (also in 0.6.7)

- ext
  - The horizontal_shard ShardedSession class accepts the common
    Session argument "query_cls" as a constructor argument,
    to enable further subclassing of ShardedQuery.
    [ticket:2090] (also in 0.6.7)

- examples
  - Updated the association, association proxy examples
    to use declarative, added a new example
    dict_of_sets_with_default.py, a "pushing the envelope"
    example of association proxy.

  - The Beaker caching example allows a "query_cls" argument
    to the query_callable() function.  [ticket:2090]
    (also in 0.6.7)

0.7.0b2
========
- orm
  - Fixed bug whereby Session.merge() would call the
    load() event with one too few arguments.
    [ticket:2053]

  - Added logic which prevents the generation of
    events from a MapperExtension or SessionExtension
    from generating do-nothing events for all the methods
    not overridden. [ticket:2052]

- declarative
  - Fixed regression whereby composite() with
    Column objects placed inline would fail
    to initialize.  The Column objects can now
    be inline with the composite() or external
    and pulled in via name or object ref.
    [ticket:2058]

  - Fix error message referencing old @classproperty
    name to reference @declared_attr [ticket:2061]
    (also in 0.6.7)

  - the dictionary at the end of the __table_args__
    tuple is now optional.  [ticket:1468]

- sql
  - Renamed the EngineEvents event class to
    ConnectionEvents.  As these classes are never
    accessed directly by end-user code, this strictly
    is a documentation change for end users.  Also
    simplified how events get linked to engines
    and connections internally. [ticket:2059]

  - The Sequence() construct, when passed a MetaData()
    object via its 'metadata' argument, will be
    included in CREATE/DROP statements within
    metadata.create_all() and metadata.drop_all(),
    including "checkfirst" logic.  [ticket:2055]

  - The Column.references() method now returns True
    if it has a foreign key referencing the
    given column exactly, not just it's parent
    table.  [ticket:2064]

- postgresql
  - Fixed regression from 0.6 where SMALLINT and
    BIGINT types would both generate SERIAL
    on an integer PK column, instead of
    SMALLINT and BIGSERIAL [ticket:2065]

- ext
  - Association proxy now has correct behavior for
    any(), has(), and contains() when proxying
    a many-to-one scalar attribute to a one-to-many
    collection (i.e. the reverse of the 'typical'
    association proxy use case)  [ticket:2054]

- examples
  - Beaker example now takes into account 'limit'
    and 'offset', bind params within embedded
    FROM clauses (like when you use union() or
    from_self()) when generating a cache key.

0.7.0b1
=======
- Detailed descriptions of each change below are
  described at:
  http://www.sqlalchemy.org/trac/wiki/07Migration

- general
  - New event system, supercedes all extensions, listeners,
    etc.  [ticket:1902]

  - Logging enhancements
    [ticket:1926]

  - Setup no longer installs a Nose plugin
    [ticket:1949]

  - The "sqlalchemy.exceptions" alias in sys.modules
    has been removed.   Base SQLA exceptions are
    available via "from sqlalchemy import exc".
    The "exceptions" alias for "exc" remains in
    "sqlalchemy" for now, it's just not patched into
    sys.modules.

- orm
  - More succinct form of query.join(target, onclause)
    [ticket:1923]

  - Hybrid Attributes, implements/supercedes synonym()
    [ticket:1903]

  - Rewrite of composites [ticket:2008]

  - Mutation Event Extension, supercedes "mutable=True"

  - PickleType and ARRAY mutability turned off by default
     [ticket:1980]

  - Simplified polymorphic_on assignment
    [ticket:1895]

  - Flushing of Orphans that have no parent is allowed
    [ticket:1912]

  - Adjusted flush accounting step to occur before
    the commit in the case of autocommit=True.  This allows
    autocommit=True to work appropriately with
    expire_on_commit=True, and also allows post-flush session
    hooks to operate in the same transactional context
    as when autocommit=False.  [ticket:2041]

  - Warnings generated when collection members, scalar referents
    not part of the flush
    [ticket:1973]

  - Non-`Table`-derived constructs can be mapped
    [ticket:1876]

  - Tuple label names in Query Improved
    [ticket:1942]

  - Mapped column attributes reference the most specific
    column first
    [ticket:1892]

  - Mapping to joins with two or more same-named columns
    requires explicit declaration
    [ticket:1896]

  - Mapper requires that polymorphic_on column be present
    in the mapped selectable
    [ticket:1875]

  - compile_mappers() renamed configure_mappers(), simplified
    configuration internals
    [ticket:1966]

  - the aliased() function, if passed a SQL FromClause element
    (i.e. not a mapped class), will return element.alias()
    instead of raising an error on AliasedClass.  [ticket:2018]

  - Session.merge() will check the version id of the incoming
    state against that of the database, assuming the mapping
    uses version ids and incoming state has a version_id
    assigned, and raise StaleDataError if they don't
    match.  [ticket:2027]

  - Session.connection(), Session.execute() accept 'bind',
    to allow execute/connection operations to participate
    in the open transaction of an engine explicitly.
    [ticket:1996]

  - Query.join(), Query.outerjoin(), eagerload(),
    eagerload_all(), others no longer allow lists
    of attributes as arguments (i.e. option([x, y, z])
    form, deprecated since 0.5)

  - ScopedSession.mapper is removed (deprecated since 0.5).

  - Horizontal shard query places 'shard_id' in
    context.attributes where it's accessible by the
    "load()" event. [ticket:2031]

  - A single contains_eager() call across
    multiple entities will indicate all collections
    along that path should load, instead of requiring
    distinct contains_eager() calls for each endpoint
    (which was never correctly documented).
    [ticket:2032]

  - The "name" field used in orm.aliased() now renders
    in the resulting SQL statement.

  - Session weak_instance_dict=False is deprecated.
    [ticket:1473]

  - An exception is raised in the unusual case that an
    append or similar event on a collection occurs after
    the parent object has been dereferenced, which
    prevents the parent from being marked as "dirty"
    in the session.  Was a warning in 0.6.6.
    [ticket:2046]

  - Query.distinct() now accepts column expressions
    as *args, interpreted by the Postgresql dialect
    as DISTINCT ON (<expr>). [ticket:1069]

  - Additional tuning to "many-to-one" relationship
    loads during a flush().   A change in version 0.6.6
    ([ticket:2002]) required that more "unnecessary" m2o
    loads during a flush could occur.   Extra loading modes have
    been added so that the SQL emitted in this
    specific use case is trimmed back, while still
    retrieving the information the flush needs in order
    to not miss anything.  [ticket:2049]

  - the value of "passive" as passed to
    attributes.get_history() should be one of the
    constants defined in the attributes package.  Sending
    True or False is deprecated.

  - Added a `name` argument to `Query.subquery()`, to allow
    a fixed name to be assigned to the alias object.
    [ticket:2030] (also in 0.6.7)

  - A warning is emitted when a joined-table inheriting mapper
    has no primary keys on the locally mapped table
    (but has pks on the superclass table).  [ticket:2019]
    (also in 0.6.7)

  - Fixed bug where "middle" class in a polymorphic hierarchy
    would have no 'polymorphic_on' column if it didn't also
    specify a 'polymorphic_identity', leading to strange
    errors upon refresh, wrong class loaded when querying
    from that target. Also emits the correct WHERE criterion
    when using single table inheritance. [ticket:2038]
    (also in 0.6.7)

 - Fixed bug where a column with a SQL or server side default
   that was excluded from a mapping with include_properties
   or exclude_properties would result in UnmappedColumnError.
   [ticket:1995] (also in 0.6.7)

  - A warning is emitted in the unusual case that an
    append or similar event on a collection occurs after
    the parent object has been dereferenced, which
    prevents the parent from being marked as "dirty"
    in the session.  This will be an exception in 0.7.
    [ticket:2046] (also in 0.6.7)

- declarative
  - Added an explicit check for the case that the name
    'metadata' is used for a column attribute on a
    declarative class. [ticket:2050] (also in 0.6.7)

- sql
  - Added over() function, method to FunctionElement
    classes, produces the _Over() construct which
    in turn generates "window functions", i.e.
    "<window function> OVER (PARTITION BY <partition by>,
    ORDER BY <order by>)".
    [ticket:1844]

  - LIMIT/OFFSET clauses now use bind parameters
    [ticket:805]

  - select.distinct() now accepts column expressions
    as *args, interpreted by the Postgresql dialect
    as DISTINCT ON (<expr>).  Note this was already
    available via passing a list to the `distinct`
    keyword argument to select(). [ticket:1069]

  - select.prefix_with() accepts multiple expressions
    (i.e. *expr), 'prefix' keyword argument to select()
    accepts a list or tuple.

  - Passing a string to the `distinct` keyword argument
    of `select()` for the purpose of emitting special
    MySQL keywords (DISTINCTROW etc.) is deprecated -
    use `prefix_with()` for this.

  - TypeDecorator works with primary key columns
    [ticket:2005] [ticket:2006]

  - DDL() constructs now escape percent signs
    [ticket:1897]

  - Table.c / MetaData.tables refined a bit, don't allow direct
    mutation  [ticket:1893] [ticket:1917]

  - Callables passed to `bindparam()` don't get evaluated
    [ticket:1950]

  - types.type_map is now private, types._type_map
    [ticket:1870]

  - Non-public Pool methods underscored
    [ticket:1982]

  - Added NULLS FIRST and NULLS LAST support. It's implemented
    as an extension to the asc() and desc() operators, called
    nullsfirst() and nullslast().  [ticket:723]

  - The Index() construct can be created inline with a Table
    definition, using strings as column names, as an alternative
    to the creation of the index outside of the Table.

  - execution_options() on Connection accepts
    "isolation_level" argument, sets transaction isolation
    level for that connection only until returned to the
    connection pool, for thsoe backends which support it
    (SQLite, Postgresql) [ticket:2001]

  - A TypeDecorator of Integer can be used with a primary key
    column, and the "autoincrement" feature of various dialects
    as well as the "sqlite_autoincrement" flag will honor
    the underlying database type as being Integer-based.
    [ticket:2005]

  - Established consistency when server_default is present
    on an Integer PK column.  SQLA doesn't pre-fetch these,
    nor do they come back in cursor.lastrowid (DBAPI).
    Ensured all backends consistently return None
    in result.inserted_primary_key for these. Regarding
    reflection for this case, reflection of an int PK col
    with a server_default sets the "autoincrement" flag to False,
    except in the case of a PG SERIAL col where we detected a
    sequence default. [ticket:2020] [ticket:2021]

  - Result-row processors are applied to pre-executed SQL
    defaults, as well as cursor.lastrowid, when determining
    the contents of result.inserted_primary_key.
    [ticket:2006]

  - Bind parameters present in the "columns clause" of a select
    are now auto-labeled like other "anonymous" clauses,
    which among other things allows their "type" to be meaningful
    when the row is fetched, as in result row processors.

  - TypeDecorator is present in the "sqlalchemy" import space.

  - Non-DBAPI errors which occur in the scope of an `execute()`
    call are now wrapped in sqlalchemy.exc.StatementError,
    and the text of the SQL statement and repr() of params
    is included.  This makes it easier to identify statement
    executions which fail before the DBAPI becomes
    involved.  [ticket:2015]

  - The concept of associating a ".bind" directly with a
    ClauseElement has been explicitly moved to Executable,
    i.e. the mixin that describes ClauseElements which represent
    engine-executable constructs.  This change is an improvement
    to internal organization and is unlikely to affect any
    real-world usage.  [ticket:2048]

  - Column.copy(), as used in table.tometadata(), copies the
    'doc' attribute.  [ticket:2028] (also in 0.6.7)

  - Added some defs to the resultproxy.c extension so that
    the extension compiles and runs on Python 2.4.
    [ticket:2023] (also in 0.6.7)

  - The compiler extension now supports overriding the default
    compilation of expression._BindParamClause including that
    the auto-generated binds within the VALUES/SET clause
    of an insert()/update() statement will also use the new
    compilation rules. [ticket:2042] (also in 0.6.7)

-sqlite
  - SQLite dialect now uses `NullPool` for file-based databases
    [ticket:1921]

  - The path given as the location of a sqlite database is now
    normalized via os.path.abspath(), so that directory changes
    within the process don't affect the ultimate location
    of a relative file path.  [ticket:2036]

- postgresql
  - When explicit sequence execution derives the name
    of the auto-generated sequence of a SERIAL column,
    which currently only occurs if implicit_returning=False,
    now accommodates if the table + column name is greater
    than 63 characters using the same logic Postgresql uses.
    [ticket:1083] (also in 0.6.7)

  - Added an additional libpq message to the list of "disconnect"
    exceptions, "could not receive data from server"
    [ticket:2044] (also in 0.6.7)

- mssql
  - the String/Unicode types, and their counterparts VARCHAR/
    NVARCHAR, emit "max" as the length when no length is
    specified, so that the default length, normally '1'
    as per SQL server documentation, is instead
    'unbounded'.  This also occurs for the VARBINARY type.
    [ticket:1833].

    This behavior makes these types more closely compatible
    with Postgresql's VARCHAR type which is similarly unbounded
    when no length is specified.

- mysql
  - New DBAPI support for pymysql, a pure Python port
    of MySQL-python.  [ticket:1991]

  - oursql dialect accepts the same "ssl" arguments in
    create_engine() as that of MySQLdb.  [ticket:2047]
    (also in 0.6.7)

- firebird
  - Some adjustments so that Interbase is supported as well.
    FB/Interbase version idents are parsed into a structure
    such as (8, 1, 1, 'interbase') or (2, 1, 588, 'firebird')
    so they can be distinguished. [ticket:1885]

- drizzle
  - New dialect for Drizzle, a MySQL variant.  Uses MySQL-python
    for the DBAPI.  [ticket:2003]