Tim,
. . . Versions solves this for
me.
Maybe like death would solve my problem with overdue taxes wink.
I did get the versioned connections to work (so far), BUT, I will
definately take your word on it and seek another solution :)
snip Like, e.g., in the ZODB 3.2 line,
otherdb
If I get a versioned connection from the ZODB:
conn = Zope.DB.open(version=myVersion)
root = conn.root()
app = root['Application']
# do some stuff
get_transaction().commit()
conn.close()
Are the changes now in a version? How do I get those changes rolled
into the trunk version of the ZODB? I
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 stuff
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
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
want to
[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 specific
