From: | Zeugswetter Andreas IZ5 <Andreas(dot)Zeugswetter(at)telecom(dot)at> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] Re: Arrays versus 'type constant' syntax |
Date: | 1999-07-15 07:35:17 |
Message-ID: | 219F68D65015D011A8E000006F8590C60339E073@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Hmm. OK, then, we're stuck with a tradeoff that (fortunately) only
> affects arrays. Is it better to force subscripted column names to be
> fully qualified "table.column[subscripts]" (the current situation),
> or to allow bare column names to be subscripted at the cost of requiring
> casts from string constants to array types to use the long-winded CAST
> notation (or nonstandard :: notation)?
>
Yes, me thinks so too.
> I would guess that the cast issue comes up *far* less frequently than
> subscripting, so we'd be better off changing the behavior. But the
> floor is open for discussion.
>
Yes.
I have this change implemented and tested here, btw, but I won't
check
it in until I see if there are objections...
I would apply it :-)
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 1999-07-15 08:33:01 | RE: [HACKERS] What does explain show ? |
Previous Message | Gene Sokolov | 1999-07-15 07:16:46 | Re: [HACKERS] Updated TODO list |