Hello zodb developers!
My product has 'Auto refresh mode' option checked.
I changed some source code of my product, after that autorefresh have been
occured.
And after autorefresh I got strange several errors:
this error was accure almost after all autorefreshs.
1.
2005-07-12 17:44:07
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
hi all!
i'm trying to form a patch that will result in a method
_before_commit()
being called on each modified object in a transaction (if that method
exists of course) right before commit.
main sense is to automate/delay
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
hi all!
i'm trying to form a patch that will result in a method
_before_commit()
being called on each modified object in a transaction (if that method
exists of course) right before commit.
main sense is
On 7/12/05, Tim Peters [EMAIL PROTECTED] wrote:
[Jeremy Hylton]
IIRC, the old implementation of savepoints kept a copy of the index at
the time the savepoint was taken so that you could rollback to it
multiple times. I don't think there's any way to avoid such a copy.
Right, and the
[Christian Heimes, suggests changing Transaction.commit() to start with
if subtransaction:
# TODO deprecate subtransactions
self._subtransaction_savepoint = self.savepoint(1)
return
if self._savepoint2index:
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
[ Jim Fulton wrote:]
Jürgen Herrmann wrote:
hi all!
i'm trying to form a patch that will result in a method
_before_commit()
being called on each modified object in a transaction (if that method
exists of course) right
Tim Peters wrote:
[Christian Heimes, suggests changing Transaction.commit() to start with
if subtransaction:
# TODO deprecate subtransactions
self._subtransaction_savepoint = self.savepoint(1)
return
if self._savepoint2index:
Jim Fulton wrote:
A good community project would be
to convert all of the subtransaction calls in Zope to
savepoint calls.
Done
I found commit(1) in Zope3 zope.app.file.file Pdata handling and in code
and tests in Zope2.
Christian
___
For more
[Jeremy Hylton]
I understand. The further invariant is that the index captured when a
savepoint created is immutable.
Or at least acts like it. Copying is an easy-to-code and effective way to
ensure that, and I don't know of a better feasible way. Capturing a lot of
savepoints (or doing a
[Jim Fulton]
A good community project would be to convert all of the subtransaction
calls in Zope to savepoint calls.
[Christian Heimes]
Done
I found commit(1) in Zope3 zope.app.file.file Pdata handling and in code
and tests in Zope2.
Bless you! Alas, I haven't received any messages from
Tim Peters wrote:
Bless you! Alas, I haven't received any messages from any Zope Corp checkin
list since Sunday, so we'll just have to take your word for it wink.
svn diff -r 33279:33280 \
svn+ssh://svn.zope.org/repos/main/Zope/branches/Zope-2_8-branch
On 7/12/05, Jens Vagelpohl [EMAIL PROTECTED] wrote:
On 12 Jul 2005, at 13:17, Victor Safronovich wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
If it creates problems then simply don't use it.
That's not a
On Jul 12, 2005, at 1:46 PM, Jens Vagelpohl wrote:
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
If it
On 7/12/05, Jens Vagelpohl [EMAIL PROTECTED] wrote:
On 12 Jul 2005, at 18:17, Lennart Regebro wrote:
previous Zope version, which I used, was 2.6.1, but it was very old
version and
I decided to jump to 2.8.0. I took problems with autorefresh. What
can I do to solve
my problems?
[Victor Safronovich, having problems with auto refresh]
Victor (et alia), I think a discussion of auto-refresh would be more useful
on a Zope list -- it's not really (AFAIK) a ZODB issue.
This is what changed in ZODB, from ZODB 3.3c1's NEWS file (and no, it won't
be changed back to the way it
[Jürgen Herrmann]
...
so, what i need is a way to have my mechanism called before transaction
commits (would be possible to use the hooks provided by zodb 3.4 for
that, sure) and cycle through all modified objects (that's where the
hooks in 3.4 are not enough for me, they don't provide any way
Imagine if somebody tried to use ZPTs, and the answer to any question
where you get errors from it is well, then don't use it? It's just
not a viable answer.
Refresh is not a core functionality like ZPT. That comparison is a
bit outlandish.
If it is the majoritys agreement that this
Sidnei da Silva wrote:
| Does't the *already included* zeoup.py do exactly what you are trying
| to do? See the bin directory of your zope home.
Unfortunately no. It uses ClientStorage, which goes through the 1000's
of lines of the connection dance using connect threads and large
timeouts.
On 7/12/05, Jens Vagelpohl [EMAIL PROTECTED] wrote:
If it is the majoritys agreement that this answer is the best one, and
that the refresh functionality should be looked at as something that
may or may not work purely on luck, then I'll mark it as deprecated
and up for removal in 2.10.
20 matches
Mail list logo
