[Etienne Labuschagne]
>>> . . . Versions solves this for me.
[Tim Peters]
>> Maybe like death would solve my problem with overdue taxes .
[Etienne]
> I did get the versioned connections to work (so far), BUT, I will
> definately take your word on it and seek another solution :)
If that works for
Tim,
> > . . . Versions solves this for
> > me.
>
> Maybe like death would solve my problem with overdue taxes .
I did get the versioned connections to work (so far), BUT, I will
definately take your word on it and seek another solution :)
> Like, e.g., in the ZODB 3.2 line,
>
> otherdb
[Etienne Labuschagne]
> ...
> I really need a "temporary" connection that I can discard. This
> connection can have a much smaller cache than the normal connections
> as it makes very little difference in the speed of data loading.
> Second prize is a connection that will only be used by a specifi
On 7/11/05, Florent Guillaume <[EMAIL PROTECTED]> wrote:
> ZODB versions are deprecated, unsupported, buggy and hard to use. Don't
> use them.
>
> Florent
And as I understand, so are temporary connections too. That leaves me
with getting a "normal" ZODB connection from the pool which I don't
wan
Please stay on the list.
On 11 Jul 2005, at 16:19, Mark Barratt wrote:
Florent Guillaume wrote:
ZODB versions are deprecated, unsupported, buggy and hard to use.
Don't
use them.
Understood. Alternative mechanisms which achieve the same object?
Well that depends on your objective, and you
ZODB versions are deprecated, unsupported, buggy and hard to use. Don't
use them.
Florent
Etienne Labuschagne <[EMAIL PROTECTED]> wrote:
> If I get a versioned connection from the ZODB:
>
> conn = Zope.DB.open(version="myVersion")
> root = conn.root()
> app = root['Application']
>
> # do some
