| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: function parse_ident |
| Date: | 2016-02-14 03:28:53 |
| Message-ID: | CAFj8pRBB1iMBWq-dz09uofMwuWQHMiQrwgcnJFoNSa5Srrhr_w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Jim
2016-02-11 8:27 GMT+01:00 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
>
>
> ok
>
>>
>> Also added test for invalid characters.
>>
>> I think "strict" would be more in line with other uses in code. There are
>> currently no other occurrences of 'strictmode' in the code. There are loads
>> of references to 'strict', but I didn't go through all of them to see if
>> any were used as externally visible function parameter names.
>>
>
> I am sorry, I don't understand to this point. You unlike the name of
> parameter "strictmode" ? Have you any proposal? Maybe "restrictive" ?
>
Please, can you explain this point?
Regards
Pavel
>
>
>>
>>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2016-02-14 05:19:38 | Re: Freeze avoidance of very large table. |
| Previous Message | Robert Haas | 2016-02-14 03:07:06 | Re: Way to check whether a particular block is on the shared_buffer? |