| From: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
|---|---|
| To: | Enrico Pirozzi <e(dot)pirozzi(at)nbsgroup(dot)it> |
| Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 9.6: view based on sequence |
| Date: | 2018-01-24 12:11:47 |
| Message-ID: | CAHjZ2x6DNC7rmpk5X36HDH2o1dtJJDM6OOJa3hwrsR5rK_bPpA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2018-01-24 13:10 GMT+01:00 Enrico Pirozzi <e(dot)pirozzi(at)nbsgroup(dot)it>:
> it's just to know why postgresql does not return a warning.
>
>
>
> Il 24/01/2018 13:06, Vincenzo Romano ha scritto:
>>
>> I haven't any v9 any more in my deployments. Sorry.
>>
>> What is the objective of that view?
>> If it's to hide the nextval() function, then the solution can be
>> similar to mine.
>> If it's to access the sequence metainfo, then maybe it'd be better to
>> explore the pg_catalog schema.
>
>
> --
> Enrico Pirozzi
> e(dot)pirozzi(at)nbsgroup(dot)it
>
Those queries are all legal. No warning is due.
--
Vincenzo Romano - NotOrAnd.IT
Information Technologies
--
NON QVIETIS MARIBVS NAVTA PERITVS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2018-01-24 12:50:10 | Re: [PATCH] Logical decoding of TRUNCATE |
| Previous Message | Enrico Pirozzi | 2018-01-24 12:10:52 | Re: PostgreSQL 9.6: view based on sequence |