Hi Todd,

I'm sorry I don't think I can help.  I was just looking at what I'm running.
I remember you talking about those changes, but it appears that I'm using
some previous version of Glorp.  It's embarrassing but I don't even know
what version I'm running.

I had to make some changes to get the postgres2 client running on squeak
3.9.  I posted a bug with the changes in mantis and sourceforge.  The
problem is I didn't copy the original versions into my repository and now
I'm on my own version 4.  I really need to go back and figure it out and
load the new squeak port to try it out.

I'm guessing my version doesn't report the errors at all.  Sorry.  Please
keep us informed if you figure out the problem or if you have a reproducible
example, I'd be happy to try it out and help you debug it.

Ron


> From: Todd Blanchard 
> Sent: Thursday, March 08, 2007 2:01 PM
> 
> postgres2, I don't have sample code because you'd need the whole data
> model with constraints and I haven't quite managed to produce a
> reproduceable case that doesn't involve sending the whole database.
> The db contains confidential information so I can't send that off.
> 
> So it is postgres2, using glorp, on Squeak 3.7.  I have noticed glorp
> doesn't catch errors on commit and changed it - but the error is not
> showing up in the result from the connection.
> 
> -Todd Blanchard
> 
> On Mar 8, 2007, at 10:53 AM, Ron Teitelbaum wrote:
> 
> > Do you have an example of the code that I can try here?  Are you
> > using the
> > postgres2 client, or the regular client?  What version of
> > postgreSQL are you
> > using?
> >
> > Ron Teitelbaum
> >
> >> -----Original Message-----
> >> From: squeak-dev-bounces at lists.squeakfoundation.org [mailto:squeak-
> >> dev-
> >> bounces at lists.squeakfoundation.org] On Behalf Of Todd Blanchard
> >> Sent: Thursday, March 08, 2007 1:30 PM
> >> To: The general-purpose Squeak developers list
> >> Subject: PostgresSQL connector fails to report some errors?
> >>
> >> I'm finding that starting a transaction, issuing a lot of updates,
> >> then committing a transaction sometimes fails to return a constraints
> >> violation error that causes the commit to fail.  Logging the sql and
> >> pasting it into the psql shell definitely displays the error - which
> >> occurs as a result of sending 'commit transaction' as the constraints
> >> are all set to deferred.
> >>
> >> Has anybody else noticed this or am I special?
> >>
> >
> >
> >
>