From: John Singleton (jsingletjohnsingleton.com)
Date: Mon Jun 07 2004 - 10:16:11 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Hi Markus,

Do you know if this will be corrected in the future? I'm trying to
figure out how to document it. If this won't be corrected in the future,
SQL Studio is limited to creating synonyms for objects the current user
owns. In theory, however, SQL Studio could create a synonym for any
object a user has privileges for.

Cheers,
JLS

Stausberg, Markus wrote:

>Hello John,
>
>you wrote :
>
>
>>I have two users, DBA, and DBA2. I also have 2 tables FOO and
>>BAR. FOO
>>belongs to DBA and BAR belongs to DBA2. DBA has all
>>privileges on DBA2's
>>tables and vice-a-versa.
>>
>>Now: In sqlcli I can use the create synonym statement to create a
>>synonym like this.
>>
>>sqlcli -d <dbname> -u DBA,password
>>
>>sqlcli on <dbname>=> CREATE PUBLIC SYNONYM S_BAR for DBA2.BAR
>>
>>This works. However whenever I try to do this in SQL Studio, I get an
>>error: (logged in as DBA)
>>
>>Auto Commit: Off, SQL Mode: Internal, Isolation Level: Committed
>>Base table not found;-4004 POS(38) Unknown table name:BAR.
>>
>>CREATE PUBLIC SYNONYM "S_BAR" FOR "BAR"
>>
>>
>
>
>The difference between the sqlcli and SQL Studio variants
>of your CREATE SYNONYM statement is the missing user(schema)
>qualification in the latter, and that produces the error.
>
>
>regards,
>
>Markus Stausberg
>SAP Labs Berlin
>
>
>
>

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]