Final words -
If you use PostGres and Hibernate, * everything * has to be in a
transaction, ALWAYS.
That and remember to close your sessions.
Thanks for listening to my rambling.
Mark
On Mon, Mar 9, 2009 at 10:31 AM, Mark Mandel wrote:
> Well, there was an issue there, in that I was
?
Mark
On Mon, Mar 9, 2009 at 10:05 AM, Mark Mandel wrote:
> Omg... i think this one was all on me
>
> What I thought was closing the connection at the end of my
> processing... doesn't look like it was.
>
> Pretty sure this has fixed it. Will let you know.
>
> M
Omg... i think this one was all on me
What I thought was closing the connection at the end of my
processing... doesn't look like it was.
Pretty sure this has fixed it. Will let you know.
Mark
On Mon, Mar 9, 2009 at 9:52 AM, Mark Mandel wrote:
> Thanks for this -
>
> I
ransaction'...
I am using JDBC connection pooling, but I was sure I was closing them
when I was done.
Mark
On Mon, Mar 9, 2009 at 8:29 AM, Scott Marlowe wrote:
> On Sun, Mar 8, 2009 at 2:54 PM, Mark Mandel wrote:
>> Just a note on this -
>>
>> I have tried it on both 8.2
be completely random, and I'm got no idea what is going on.
Thanks in advance.
Mark
On Sun, Mar 8, 2009 at 11:39 AM, Mark Mandel wrote:
> All,
>
> I seem to have a weird one here.
>
> I'm using Hibernate on my application to generate my DDL for postGres
> whenev
All,
I seem to have a weird one here.
I'm using Hibernate on my application to generate my DDL for postGres
whenever it starts up, so when doing automated testing, the database
tends to get tables and constrains dropped quite regularly, so as to
have stable test data to work from in each test.
O