From: Mike Bayer <mike_mp@zzzcomputing.com>
Date: Mon, 6 Mar 2017 21:50:13 +0000 (-0500)
Subject: - update asktom link, fixes #3925
X-Git-Tag: rel_1_0_18~33
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d22029bfc66739bdb8b83f13069599b06adcb4af;p=thirdparty%2Fsqlalchemy%2Fsqlalchemy.git

- update asktom link, fixes #3925

Change-Id: Ibd63311dfccebbdf67e8ad7dc56ad311bf573895
(cherry picked from commit 3a6b75870bdc7aa8fe70296cc3fc94ea06f16417)
---

diff --git a/lib/sqlalchemy/dialects/oracle/base.py b/lib/sqlalchemy/dialects/oracle/base.py
index d59ee6271c..e060d94fd3 100644
--- a/lib/sqlalchemy/dialects/oracle/base.py
+++ b/lib/sqlalchemy/dialects/oracle/base.py
@@ -74,7 +74,7 @@ LIMIT/OFFSET Support
 Oracle has no support for the LIMIT or OFFSET keywords.  SQLAlchemy uses
 a wrapped subquery approach in conjunction with ROWNUM.  The exact methodology
 is taken from
-http://www.oracle.com/technology/oramag/oracle/06-sep/o56asktom.html .
+http://www.oracle.com/technetwork/issue-archive/2006/06-sep/o56asktom-086197.html .
 
 There are two options which affect its behavior: