diff options
| author | David M <davidmj@users.sourceforge.net> | 2006-07-09 05:09:37 +0000 |
|---|---|---|
| committer | David M <davidmj@users.sourceforge.net> | 2006-07-09 05:09:37 +0000 |
| commit | 0424200ac653a7b9f47ba0d038b944730e445bdb (patch) | |
| tree | 275f74a4044fa7ae792cef977c614105ab22ee11 /phpBB/includes/acm | |
| parent | 9ab98d0d79db143a1192f51746f9c8ef34119653 (diff) | |
| download | forums-0424200ac653a7b9f47ba0d038b944730e445bdb.tar forums-0424200ac653a7b9f47ba0d038b944730e445bdb.tar.gz forums-0424200ac653a7b9f47ba0d038b944730e445bdb.tar.bz2 forums-0424200ac653a7b9f47ba0d038b944730e445bdb.tar.xz forums-0424200ac653a7b9f47ba0d038b944730e445bdb.zip | |
Short story: Oracle does not like sub queries that contain columns that have the same name
Long story: Expanding the implicitly defined columns to explicitly defined columns lets us determine which columns we are actually grabbing. This lets us avoid the problem of having two columns having the same name even though one is implicit and the other is explicit.
What does this mean? It means that when doing a limit on Oracle with an implicit column and a bunch of explicit columns, the explicit columns are the ones that "win".
git-svn-id: file:///svn/phpbb/trunk@6159 89ea8834-ac86-4346-8a33-228a782c2dd0
Diffstat (limited to 'phpBB/includes/acm')
0 files changed, 0 insertions, 0 deletions