You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sql>SELECT users.name, users.fullname, schemas.name
more> FROM sys.users, sys.schemas
more> WHERE users.default_schema = schemas.id;
SELECT: no such column 'u.name'
It is unclear where the "u" comes from. Next is is unclear why this fails.
I experimented with the FROM clause to add aliases, or drop the sys. part, but all fails with the same error message.
This is actually what I observed from test sql/test/BugTracker/authorization.SF-1430616.
Date: 2011-01-26 13:43:55 +0100
From: @grobian
To: SQL devs <>
Version: 11.1.1 (Mar2011) [obsolete]
CC: @njnes
Last updated: 2011-03-28 17:31:25 +0200
Comment 15441
Date: 2011-01-26 13:43:55 +0100
From: @grobian
sql>SELECT users.name, users.fullname, schemas.name
more> FROM sys.users, sys.schemas
more> WHERE users.default_schema = schemas.id;
SELECT: no such column 'u.name'
It is unclear where the "u" comes from. Next is is unclear why this fails.
I experimented with the FROM clause to add aliases, or drop the sys. part, but all fails with the same error message.
This is actually what I observed from test sql/test/BugTracker/authorization.SF-1430616.
Comment 15442
Date: 2011-01-26 15:10:23 +0100
From: @sjoerdmullender
Simpler failing query:
select * from users;
The problem seems to be with the definition of sys.users (a view).
Comment 15443
Date: 2011-01-26 15:13:33 +0100
From: @grobian
that makes sense!
Comment 15557
Date: 2011-03-09 17:32:28 +0100
From: @njnes
the bug was fixed (by proper naming/resolving of view columns)
Comment 15618
Date: 2011-03-28 17:31:25 +0200
From: @sjoerdmullender
The Mar2011 version has been released.
The text was updated successfully, but these errors were encountered: