|
Archives of the TeradataForumMessage Posted: Mon, 10 Sep 2012 @ 13:59:01 GMT
Just thinking this through a bit more... From what Marek has pointed out: - the 3523 is for object level (table, view, etc) accessrights - the 5315 is for column level accessrights From the post by A Surya Kumar, - with TD13 the column level accessrights were checked first - with TD14 the object level accessrights are checked first However, on my TD14 Express system (14.0.0.1) I have an UPDATE statement that fails with a 5315 as shown below: UPDATE DBC.DATABASESPACE SET PEAKPERMSPACE = CURRENTPERMSPACE WHERE MAXPERMSPACE > 0; *** Failure 5315 The user does not have UPDATE access to DBC.DataBaseSpace.PeakPermSpace. Statement# 1, Info =0 *** Total elapsed time was 1 second. On this system the user in question has SELECT against the DatabaseSpaceTable but no other accessrights on it. So why did it fail with 5315 and not a 3523 ? I've had a (very) quick look on TaYS but cannot see anything. Cheers, Dave Ward Analytics Ltd - Information in motion (www.ward-analytics.com)
| ||||||||||||||||||||||||||||||||||||||||||||||||
| ||||||||||||||||||||||||||||||||||||||||||||||||
Copyright 2016 - All Rights Reserved | ||||||||||||||||||||||||||||||||||||||||||||||||
Last Modified: 15 Jun 2023 | ||||||||||||||||||||||||||||||||||||||||||||||||