Michael,
You have name A for 'create index' and name B for 'drop index'
I can think that it isn't same index
This is illogically for me
make object with name A and drop it with name B
> If the schema was allowed, some people would infer that they
> can place the index in a schema other than the schema the table
> resides in, and they would get bitten when they try to do so.
you can just return error (and you will enable indexes cross schema
later, maybe and you will not change syntax)
Thanks
On Sunday 09 April 2006 04:48 am, Michael Glaesemann wrote:
>
> On Apr 9, 2006, at 13:33 , Haris Peco wrote:
>
> > create index test.test_name on test.test(name)
> >
> > schema prefix in 'create index'
> >
> > I know that it isn't necessary, because postgreSQL know that index
> > is (must be)
> > in table's schema, but this is natural for sql writers
>
> Allowing a schema-qualified name for CREATE INDEX implies that there
> is a choice of schema you could choose. By disallowing the schema, it
> makes developers aware of the limitation of where the index can be
> created. If the schema was allowed, some people would infer that they
> can place the index in a schema other than the schema the table
> resides in, and they would get bitten when they try to do so.
>
> Michael Glaesemann
> grzm myrealbox com
>
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo@postgresql.org so that your
> message can get through to the mailing list cleanly
>
