Re: Truncation of object names

ncm@zembu.com (Nathan Myers) writes:
> Sorry, false alarm.  When I got the test case, it turned out to
> be the more familiar problem:

>   create table foo_..._bar1 (id1 ...);
>     [notice, "foo_..._bar1" truncated to "foo_..._bar"]
>   create table foo_..._bar (id2 ...);
>     [error, foo_..._bar already exists]
>   create index foo_..._bar_ix on foo_..._bar(id2);
>     [notice, "foo_..._bar_ix" truncated to "foo_..._bar"]
>     [error, foo_..._bar already exists]
>     [error, attribute "id2" not found]

> It would be more helpful for the first "create" to fail so we don't 
> end up cluttered with objects that shouldn't exist, and which interfere
> with operations on objects which should.

Seems to me that if you want a bunch of CREATEs to be mutually
dependent, then you wrap them all in a BEGIN/END block.

			regards, tom lane