Hello!
I think I have a kind of deja vu.
Coming back to the early version of SAP DB
(I think something about 7.3.0.18 or 7.3.0.20)
I remember reporting the bug about using sequences
in stored procedures.
Luckily this isn't very serious and the workaround isn't too much
complicated :-)
The problem is that a user who wants to use a stored procedure
which operates on counters (e.g. NEXTVAL) must have
explicit privileges to use that counters (granting a privilege
EXECUTE to this stored procedure isn't enough).
I remember that was fixed long, long ago, however,
few weeks ago I've migrated  to the latest version of MaxDB
(7.5.0.26) and "guess who is here"?
Yes, it seems that somehow the old bug is reintroduced.
Steps to reproduce:
1. Create a user APP_ADMIN.(type - DBA)
2. Create a user APP_USER (type - STANDARD)
2. Log on using APP_ADMIN.
3. Create Sequence CNT_TEST.
4. Create Stored Procedure SP_TEST that is operating on CNT_TEST.
5. Grant an EXECUTE privilege to the user APP_USER for SP_TEST.
6. Log on using APP_USER.
7. Try to execute SP_TEST.
In my case, the error saying that "the counter CNT_TEST wasn't found"
is reported.
Could anyone confirm?
Thanks a lot for your support and patience ;-)

Best regards,
Marcin Pytel


-- 
 




-- 
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to