Yes, except we need to use this with Hibernate, and I'm struggling to do so
with the work around and utilizing the same connection for the whole
Hibernate transaction. Being able to have this working as it should would
be a great help.

cheers,

David



|---------+----------------------------->
| | "Roman Rokytskyy" |
| | <rrokytskyy@...|
| | g> |
| | Sent by: |
| | Firebird-Java@yaho|
| | ogroups.com |
| | |
| | |
| | 01/30/2006 02:32 |
| | AM |
| | Please respond to |
| | Firebird-Java |
| | |
|---------+----------------------------->

>------------------------------------------------------------------------------------------------------------------------------|

| |
| To: <Firebird-Java@yahoogroups.com> |
| cc: |
| Subject: Re: More Info on Re: [Firebird-Java] connection-connection vs connection-isql transaction locking |
| wierdness |

>------------------------------------------------------------------------------------------------------------------------------|




> Will you post to the dev list, or should I send a note?

I will send it directly to Dmitry or Vlad, also cc-ed to devel.

> As I mentioned before, we are really under the gun timewise on this, so
> your help is greatly appreciated.

But as I understand, you have found a workaround for the issue - you have
to
ensure that first SQL is an update, right?

Roman




Yahoo! Groups Links