Re: user can't access own database after creation

Yes, JDBC is still involved. I'd say there is a mistake in the JPA config

Dave Cramer

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

On 2 December 2015 at 17:15, Nuno Zimas <nzimas(at)gmail(dot)com> wrote:

> The programmer says that she relies on JPA to establish the connection,
> but I suppose that JDBC is still involved, otherwise i can’t see how java
> would talk to postgresql.
> Unless JPA does so directly.
> Like I said, Java really isn’t my thing.
>
>
>
> On 2 Dec 2015, at 22:05, Nuno Zimas <nzimas(at)gmail(dot)com> wrote:
>
>
> Thanks a lot, everyone (and specially Dave Cramer).
> Now I know the issue is not JDBC related.
> Not sure of this is good news for me, though :)
>
> I’d think that the application needs to be amended.
> Still, this does not account for the fact that it works on a local win
> machine.
>
> As you can see, Dave’s little program connects like a charm,
>
> 2015-12-02 17:00:22 EST [2408-1] postgres(at)postgres LOG: duration: 16.239
> ms parse <unnamed>: SET extra_float_digits = 3
> 2015-12-02 17:00:22 EST [2408-2] postgres(at)postgres LOG: duration: 0.023
> ms bind <unnamed>: SET extra_float_digits = 3
> 2015-12-02 17:00:22 EST [2408-3] postgres(at)postgres LOG: duration: 0.031
> ms execute <unnamed>: SET extra_float_digits = 3
> 2015-12-02 17:00:22 EST [2408-4] postgres(at)postgres LOG: duration: 0.217
> ms parse <unnamed>: select 1
> 2015-12-02 17:00:22 EST [2408-5] postgres(at)postgres LOG: duration: 0.100
> ms bind <unnamed>: select 1
> 2015-12-02 17:00:22 EST [2408-6] postgres(at)postgres LOG: duration: 0.953
> ms execute <unnamed>: select 1
>
>
>
> On 2 Dec 2015, at 21:45, Dave Cramer <pg(at)fastcrypt(dot)com> wrote:
>
> log_min_duration
>
>
>
>