From bd3a65252d2f9155b7f2c1c6284074ba6e555d1f Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sat, 19 Jan 2008 20:11:29 +0000 Subject: - Oracle assembles the correct columns in the result set column mapping when generating a LIMIT/OFFSET subquery, allows columns to map properly to result sets even if long-name truncation kicks in [ticket:941] --- lib/sqlalchemy/databases/oracle.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/sqlalchemy/databases') diff --git a/lib/sqlalchemy/databases/oracle.py b/lib/sqlalchemy/databases/oracle.py index c7ab13441..55bdf74b1 100644 --- a/lib/sqlalchemy/databases/oracle.py +++ b/lib/sqlalchemy/databases/oracle.py @@ -675,7 +675,7 @@ class OracleCompiler(compiler.DefaultCompiler): limitselect.append_whereclause("ora_rn<=%d" % (select._limit + select._offset)) else: limitselect.append_whereclause("ora_rn<=%d" % select._limit) - return self.process(limitselect, **kwargs) + return self.process(limitselect, iswrapper=True, **kwargs) else: return compiler.DefaultCompiler.visit_select(self, select, **kwargs) -- cgit v1.2.1