From 85d335b01bf64a27e99cee915205afd99e7191b5 Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Thu, 11 Feb 2010 19:33:06 +0000 Subject: - The type/expression system now does a more complete job of determining the return type from an expression as well as the adaptation of the Python operator into a SQL operator, based on the full left/right/operator of the given expression. In particular the date/time/interval system created for Postgresql EXTRACT in [ticket:1647] has now been generalized into the type system. The previous behavior which often occured of an expression "column + literal" forcing the type of "literal" to be the same as that of "column" will now usually not occur - the type of "literal" is first derived from the Python type of the literal, assuming standard native Python types + date types, before falling back to that of the known type on the other side of the expression. Also part of [ticket:1683]. --- test/dialect/test_postgresql.py | 1 + 1 file changed, 1 insertion(+) (limited to 'test/dialect/test_postgresql.py') diff --git a/test/dialect/test_postgresql.py b/test/dialect/test_postgresql.py index 952f633ae..fbbc394c9 100644 --- a/test/dialect/test_postgresql.py +++ b/test/dialect/test_postgresql.py @@ -113,6 +113,7 @@ class CompileTest(TestBase, AssertsCompiledSQL): for field in 'year', 'month', 'day', 'epoch', 'hour': for expr, compiled_expr in [ + ( t.c.col1, "t.col1 :: timestamp" ), ( t.c.col2, "t.col2 :: date" ), ( t.c.col3, "t.col3 :: time" ), -- cgit v1.2.1