Re: attndims, typndims still not enforced, but make the value within a sane threshold
| От | Tom Lane |
|---|---|
| Тема | Re: attndims, typndims still not enforced, but make the value within a sane threshold |
| Дата | |
| Msg-id | 2003574.1735250916@sss.pgh.pa.us обсуждение |
| Ответ на | Re: attndims, typndims still not enforced, but make the value within a sane threshold (Bruce Momjian <bruce@momjian.us>) |
| Ответы |
Re: attndims, typndims still not enforced, but make the value within a sane threshold
|
| Список | pgsql-hackers |
Bruce Momjian <bruce@momjian.us> writes:
> So, if users are referencing attndims and the values are not accurate,
> how useful are they? I was suggesting removal so people would stop
> relying on inaccurate information, or we correct attndims to be
> accurate. Allowing people to continue relying on inaccurate information
> seems like the worst of all options.
I think removal is not happening. The documentation for attndims
already says
Number of dimensions, if the column is an array type; otherwise
0. (Presently, the number of dimensions of an array is not
enforced, so any nonzero value effectively means “it's an array”.)
and as far as I know that is completely correct. (Hence, your gripe
is not that it's not "accurate", rather that it's not "precise".)
There isn't a comparable disclaimer under typndims, but there probably
should be.
regards, tom lane
В списке pgsql-hackers по дате отправления: