On 3/2/19 11:06 AM, Lester Caine les...@lsces.co.uk [firebird-support]
wrote:
>
>
> I think I will probably have to add some extra logic into this problem,
> but it SHOULD be simple enough ...
>
> Table with three fields - Gallery_No, Image_No, Item_position
>
> A gallery can consist of any
On 02/03/2019 16:24, Lester Caine les...@lsces.co.uk [firebird-support]
wrote:
> On 02/03/2019 16:06, Lester caineles...@lsces.co.uk [firebird-support]
> wrote:
>> In the past ( 20 years ago;) ) I would simply have added a second
>> position column which is consecutive numbers and reordered
On 02/03/2019 16:06, Lester Caine les...@lsces.co.uk [firebird-support]
wrote:
> In the past ( 20 years ago;) ) I would simply have added a second
> position column which is consecutive numbers and reordered them when
> changes are made, but I'm wondering if with all the things that have
> been
I think I will probably have to add some extra logic into this problem,
but it SHOULD be simple enough ...
Table with three fields - Gallery_No, Image_No, Item_position
A gallery can consist of any number of images but we normally only
display a selection of up to 30. Item_position is a FLOAT
I see that you have only 1024 page buffers.
Do you use SuperServer or Classic?
If Superserver then increase it.
Regards,
Karol Bieniaszewski
02.03.2019 10:50, Karol Bieniaszewski liviusliv...@poczta.onet.pl
[firebird-support] wrote:
> You have quite big fill 94%, that there is a chence that new page must be
> allocated – but
> here still you have free slots.
It may be a sign of record fragmentation which is bad from performance
You have 91345 versions but Max versions is 1. Then i do not think that
performance problem is here.
You have quite big fill 94%, that there is a chence that new page must be
allocated – but here still you have free slots.
You have gap between oldest active nad next transaction. It is not big
