pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: marcmuel (@marcmuel) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
Date: Fri, 08 Oct 2021 08:31:57 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

I think the better approach would be to give Pgconnection, PgPreparedStatement and PgResultSet his dedicated instance of TimestampUtil. So, you don’t have to synchronize it and there is no danger of deadlocks. It's only a little more of memory and with lazy loading unnecessary creation can be omitted.
I also think this would be a great benefit to have "partial" thread safety.

So, Microsoft SQL jdbc for example states:
[SQLServerConnection is not thread-safe, however multiple statements created from a single connection can be processing simultaneously in concurrent threads.](https://docs.microsoft.com/en-us/sql/connect/jdbc/reference/sqlserverconnection-class?view=sql-serve...)

view thread (29+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://pgjdbc/pgjdbc
  Cc: [email protected], [email protected]
  Subject: Re: [pgjdbc/pgjdbc] PR #943: fix: synchronize modification of shared calendar (#921)
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox