The only other thing I can think of is that I did an upgrade to 2.12.0
On Thu, Aug 4, 2022 at 12:52 PM John Smith wrote:
> Personally I think there is some sort of index corruption. I dropped the
> table and recreated it and my problem went away.
> I never restarted the application and it
Personally I think there is some sort of index corruption. I dropped the
table and recreated it and my problem went away.
I never restarted the application and it started to work again.
Maybe you can make a copy of your table, insert the data fresh and point
your app to the copied table. And see
Let me know if that makes any sense, because the test data is the same and
the application code is the same. Only dropped and created the table again
using DbEaver.
On Wed, Aug 3, 2022 at 11:39 AM John Smith wrote:
> Hi, so I dropped the table and simply recreated it. Did NOT restart the
>
