> On 19 Oct 2023, at 15:55, Phil Thompson via Development
> wrote:
>
> On 19/10/2023 12:07, Giuseppe D'Angelo via Development wrote:
>> On 19/10/2023 12:07, Phil Thompson via Development wrote:
>>> Up until v6.6 upgrading to a new version was relatively low risk but this
>>> will just
> On 19 Oct 2023, at 13:07, Giuseppe D'Angelo via Development
> wrote:
>
> On 19/10/2023 12:07, Phil Thompson via Development wrote:
>> Up until v6.6 upgrading to a new version was relatively low risk but this
>> will just encourage people to stay on older versions. Is this a mistake or a
>>
On 19/10/2023 12:07, Giuseppe D'Angelo via Development wrote:
On 19/10/2023 12:07, Phil Thompson via Development wrote:
Up until v6.6 upgrading to a new version was relatively low risk but
this will just encourage people to stay on older versions. Is this a
mistake or a change in policy?
On 19/10/2023 12:07, Phil Thompson via Development wrote:
Up until v6.6 upgrading to a new version was relatively low risk but
this will just encourage people to stay on older versions. Is this a
mistake or a change in policy?
There is actually a policy document that says that certain source
Hi,
A number of API elements have been removed in v6.6.0. I haven't got an
exhaustive list but QSqlResult::boundValues() will do as an example.
The pre-6.6 implementation has been replaced by 2 new, incompatible,
overloads. I completely agree with the reasons why this was desirable,
my
