Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Will Landstrom asked, for IDS 9.4, what happens to the original table if someone creates an index on a synonym for a table in another database on another server. Art S. Kagel doubted an index can be created on a synonym at all. Kernoal Stephens replied that this gives error -556, Cannot create, drop, or modify an object that is external to the current database. Answered.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi everyone. Kind of a sanity check question. On IDS 9.4...If we have tableA
in DB1 (which is on server S1) and the a SYNONYM for tableA defined in DB2 (on
server S2) and someone were to create an INDEX on the SYNONYM...what do expect
would happen to the original tableA? I would expect nothing would happen? And
in particular of course no index would be created on the original tableA. Does
that sound correct?
Thanks, Will
WILL LANDSTROM wrote:
> Hi everyone. Kind of a sanity check question. On IDS 9.4...If we have tableA
> in DB1 (which is on server S1) and the a SYNONYM for tableA defined in DB2
(on
> server S2) and someone were to create an INDEX on the SYNONYM...what do
expect
> would happen to the original tableA? I would expect nothing would happen? And
> in particular of course no index would be created on the original tableA.
Does
> that sound correct?
>
> Thanks, Will
Don't think you CAN create an index on a synonym anyway.
Art S. Kagel
Oninit
================================================================================
===========
Please access the attached hyperlink for an important electronic
communications disclaimer:
http://www.oninit.com/home/disclaimer.php
================================================================================
===========
Clarification...
Hi everyone. Kind of a sanity check question. On IDS 9.4...If we have tableA
in Informix database01 (which is on server S1) and the a SYNONYM for tableA
defined in Informix database02 (on server S2) and someone were to create an
INDEX on the SYNONYM...what do expect would happen to the original tableA? I
would expect nothing would happen? And in particular of course no index would
be created on the original tableA. Does that sound correct?
Thanks, Will
"WILL LANDSTROM" <willlandstrom@yahoo.com>
Sent by: ids-bounces@iiug.org
02/13/2008 12:32 PM
Please respond to
ids@iiug.org
To
ids@iiug.org
cc
Subject
Index on a synonym? [11304]
Hi everyone. Kind of a sanity check question. On IDS 9.4...If we have
tableA
in DB1 (which is on server S1) and the a SYNONYM for tableA defined in DB2
(on
server S2) and someone were to create an INDEX on the SYNONYM...what do
expect
would happen to the original tableA? I would expect nothing would happen?
And
in particular of course no index would be created on the original tableA.
Does
that sound correct?
Thanks, Will
*******************************************************************************
Forum Note: Use "Reply" to post a response in the discussion forum.
See you at the IIUG Informix 2008 Conference
The Power Conference for Informix Professionals
April 27 - 30, 2008 Marriott Overland Park (Kansas City), Kansas
http://www.iiug.org/conf
Registration Now Open!!
You will get a -556 error:
Cannot create, drop, or modify an object that is external to current
database.
This statement attempts to create, drop, or alter an object in an
external database, one other than the current database. You can only
read the contents of an external database.
If you make the external database your current database, you can
modify the contents. Review all uses of names beginning with <dbname>,
which refers to an object in the external database <dbname>
Kernoal
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.