On 1/15/24 17:59, Arbol One wrote:
Bro., is in the OP.
1) I am not your Bro.
2) When troubleshooting explicit is better then implicit. What is
obvious to you might not be obvious others. I have more then once
assumed and not verified and gone down a long trail of troubleshooting
only to find the solution became clear only when the assumptions where
verified or not.
3) You still have not answered if there where errors and if so what they
are?
4) In conclusion, the sum total of your issue statement is something
worked now it doesn't. That will not get an answer other then yes you
have a problem.
-------------
I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian
15.5-1.pgdg120+1)),
postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed mode,
sharing)
and, yes... Debian 12.
For some reason NB is not longer able to interact with PG since the last
PG package update from Debian.
Is anyone else experiencing the same problem, or is it just me; I wonder.
The question is, how can I tackle this issue.
Thanks in advance.
---------------
On 2024-01-15 6:22 p.m., Adrian Klaver wrote:
On 1/15/24 14:38, Arbol One wrote:
Netbeans 20. Sorry, my bad.
And the rest of the questions?
On 2024-01-15 4:48 p.m., Adrian Klaver wrote:
On 1/15/24 13:33, Arbol One wrote:
I am working on an application using NB-20,
PG-psql (16.1 (Debian 16.1-1.pgdg120+1), server 15.5 (Debian
15.5-1.pgdg120+1)),
postgresql-42.7.0.jar.
openjdk 17.0.9 2023-10-17
OpenJDK Runtime Environment (build 17.0.9+9-Debian-1deb12u1)
OpenJDK 64-Bit Server VM (build 17.0.9+9-Debian-1deb12u1, mixed
mode, sharing)
and, yes... Debian 12.
Fo.r some reason NB is not longer able to interact with PG since the
last
Define NB.
Error messages are?
PG package update from Debian.
Update from what to what?
Is anyone else experiencing the same problem, or is it just me; I
wonder.
The question is, how can I tackle this issue.
Thanks in advance.
--
Adrian Klaver
adrian.klaver@xxxxxxxxxxx
