| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | Alexandru Lazarev <alexandru(dot)lazarev(at)gmail(dot)com> |
| Cc: | david(dot)g(dot)johnston(at)gmail(dot)com, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, "pgsql-sql(at)postgresql(dot)org" <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: Fwd: How does PostgreSQL serializable transaction works? (SELECT/UPDATE vs INSERT conflict) |
| Date: | 2016-03-10 19:58:52 |
| Message-ID: | CACjxUsOZCYZM_NKi3PcBiVgcNd=1JOKXV+-J0wLL8+-6Z5MhKg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-sql |
On Thu, Mar 10, 2016 at 1:50 PM, Alexandru Lazarev
<alexandru(dot)lazarev(at)gmail(dot)com> wrote:
> One more "offtop" question - What kind of frameworks do
> automatically retries for failed transactions? Are
> Hibernate/Spring in that list?
I have seen that done in Hibernate/Spring using dependency
injection to create a transaction manager with the necessary logic.
I was told by the developer that doing so was not trivial, but not
outrageously hard, either.
Every framework may have a different way to do this; I would just
say that any framework which does not provide a reasonable
mechanism for implementing such behavior is not one I would
consider to be mature enough for "prime time" -- although others
might feel differently.
Kevin Grittner
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alka Gupta | 2016-03-10 20:05:18 | recovering database from a linux file system |
| Previous Message | Andy Colson | 2016-03-10 19:56:40 | Re: Best approach for multi-database system |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2016-03-13 23:13:52 | Re: Subselect left join / not exists() |
| Previous Message | Alexandru Lazarev | 2016-03-10 19:50:48 | Re: [GENERAL] Fwd: How does PostgreSQL serializable transaction works? (SELECT/UPDATE vs INSERT conflict) |