Re: postgresql-jdbc driver not respecting prepareThreshold=0

Done

Dave Cramer

davec(at)postgresintl(dot)com
www.postgresintl.com

On 3 February 2017 at 10:03, Jorge Solórzano <jorsol(at)gmail(dot)com> wrote:

> Great, in that case, can you please merge https://github.com/pgjdbc/www/
> pull/41 to prepare a PR for the move?
>
>
>
>
> On Fri, Feb 3, 2017 at 8:57 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
>> On 3 February 2017 at 09:52, Jorge Solórzano <jorsol(at)gmail(dot)com> wrote:
>>
>>>
>>> On Fri, Feb 3, 2017 at 8:24 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>>>
>>>>
>>>> On 3 February 2017 at 09:16, Jorge Solórzano <jorsol(at)gmail(dot)com> wrote:
>>>>
>>>>> On Fri, Feb 3, 2017 at 7:56 AM, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>>>>>
>>>>>>
>>>>>> Sorry for not looking this up myself, but have you provided an
>>>>>> updated documentation patch then ?
>>>>>>
>>>>>>
>>>>> Well, apart ​from the connection parameter in
>>>>> https://jdbc.postgresql.org/documentation/head/connect.html there is
>>>>> no section about logging, let me send a patch for that with the new
>>>>> connection properties (there are already updated in the README.md).
>>>>>
>>>>> BTW, I think that the documentation (and the website in general) is
>>>>> getting outdated, after the release maybe someone focus on a fresh site.
>>>>>
>>>>> Maybe this have been asked before, but, is not better to have the
>>>>> documentation along with the driver? maybe use the standard /docs folder so
>>>>> it's easier to use GitHub Pages.
>>>>>
>>>>
>>>> The patch would have to be against the www site.
>>>>
>>>> I'm not in favour of moving it to github. It is owned by the postgresql
>>>> group, and should remain there.
>>>>
>>>
>>>
>>> Maybe I express me bad, ​I'm not saying to move the hosting to GitHub, I
>>> mean to move the *www/documentation/head* into *pgjdbc/docs*. that
>>> probably would require a 2 step generation and publish of the documentation
>>> (I'm not aware of the current process of the update to
>>> jdbc.postgresql.org) but it will simplify a lot making a single PR with
>>> a change and update to documentation, and "additionally" contributors can
>>> enable GitHub pages for their forks to see real changes made to docs.
>>>
>>>
>>>
>> The current process is manual, I have to do it, as I am the only one who
>> has access to the machine that hosts jdbc.postgresql.org
>>
>> I'm in favour of moving it.
>>
>>
>>
>> Dave Cramer
>>
>> davec(at)postgresintl(dot)com
>> www.postgresintl.com
>>
>>
>