Dieter Maurer wrote:
So, you got sucked into the myth of SQL too? ;-)
You'll need to rewrite at least some of your SQL if you change backends, so I
don't see this as a huge problem...
What an argument :-(
As you need to change *something*, why bother with ideas to
change as little as possibl
Clemens Robbenhaar wrote:
As I understand we agree on the original point of the discussion.
Cool, I'll make the change when I get a chance :-)
Chris
--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
___
Chris Withers wrote at 2004-3-29 16:54 +0100:
>Clemens Robbenhaar wrote:
>> But it is a base exception class in ZOracleDA, however. Thus the
>> product using it need to explicitely import this exception, and thus
>> explicitely depend on the used relational database; code needs to be
>> rewritten
Chris Withers writes:
> Clemens Robbenhaar wrote:
> > But it is a base exception class in ZOracleDA, however. Thus the
> > product using it need to explicitely import this exception, and thus
> > explicitely depend on the used relational database; code needs to be
> > rewritten if one exchan
Clemens Robbenhaar wrote:
But it is a base exception class in ZOracleDA, however. Thus the
product using it need to explicitely import this exception, and thus
explicitely depend on the used relational database; code needs to be
rewritten if one exchanges the external data base.
So, you got sucked
Chris Withers writes:
> Clemens Robbenhaar wrote:
>
> > Hm, figuring out the "right" exception actually the problem; if the
> > data base connector would raise an exception of a certain type due to
> > unability to connect I could catch these and let the others pass.
>
> Which DA are you
Clemens Robbenhaar wrote:
Hm, figuring out the "right" exception actually the problem; if the
data base connector would raise an exception of a certain type due to
unability to connect I could catch these and let the others pass.
Which DA are you using? It _should_ do that...
Unfortunately I am
Chris Withers writes:
> Clemens Robbenhaar wrote:
> > Ok, if this is the proper dance to catch such exceptions with Zope
> > without risking ZODB corruption I will go with it. So far I have not
> > been sure, that ConflictError is the only type needing special
> > treatement in these cases.
