, and reply to
confirmation mail keeping subject intact. You should then receive
subscription confirmation.
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev
be wondefull.
BTrees have a very nice API, which allow scanning only a subset of keys
by providing min and max boundaries:
for key, value in some_btree.items(
min='aa', max='b', excludemax=True):
# Do stuff
should do what you want.
http://pythonhosted.org/BTrees/
--
Vincent
this better), but
at least to use (db_id, _p_oid) as a cache key.
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
transactions are committing to try to find points at which
databases are globally consistent. It does its job so far, but
beware: it won't resist malicious usage (trivial to DoS).
[1] https://pypi.python.org/pypi/Products.TIDStorage
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
/comment ?
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
side. I encourage you to read the
code to be sure (no need to read all of it, but there are helpful docs,
comments docstrigns all over ZODB code). Check http://www.zodb.org too.
--
Vincent Pelletier
___
For more information about ZODB, see http
On Mon, 27 Aug 2012 14:37:37 +0200,
Vincent Pelletier vinc...@nexedi.com wrote :
Under the hood, it relies on simple features of SQL databases
To make things maybe a bit clearer, from the feedback I get:
You can forget about SQL presence. NEO usage of SQL is as a relational
as a handful
experience with blob handling ourselves (which is
why we preferred to leave it asides rather than providing an
unrealistic - and hence unusable - implementation).
[1]http://git.erp5.org/gitweb/neoppod.git/blob/75d83690bd4a34cfe5ed83c949e4a32c7dec7c82:/neo/storage/database/btree.py
Regards,
--
Vincent
/neoppod.git/blob/HEAD:/CHANGES
NEO is published on pypi as neoppod:
http://pypi.python.org/pypi/neoppod
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev
be obviously
separated.
Maybe a @property taking care of creating the actual PersistentDict if not
present, then ?
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https
, and I've been bitten by it when
moving from Zope 2.8 to 2.12 (maybe 2.11 too ?) as 2.8 PythonScript objects
were modified on load on the new version (adding a trailing \n IIRC), which
broke History ZMI tab: one cannot alter a non-current object revision.
--
Vincent Pelletier
in the object tree
that object is. If you have varied classes, and significant data on your
persistent instances, it will be easy.
Ragards,
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev
ZODB back-end. If ran on a
big-enough (compared to available RAM and disk speed) ZODB, it will start
causing problems, though.
Regards,
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev
a string.
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
of it (if constrained by backward
compatibility). When you must have a hot spot, design so that solving its
conflicts:
- is feasible (ie, there is one answer to enough conflict cases to be
actually useful)
- can be done without accessing any other object
Regards,
--
Vincent Pelletier
PS: I
inter-database dependencies are one-way.
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
, that is.
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
Le mercredi 12 octobre 2011 11:55:43, Vincent Pelletier a écrit :
distributed
Woops. Networked lock server. Not distributed.
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
___
For more information about ZODB, see http
possible race conditions in test cases, even knowing the code...
Ideas ?
Of course, I (as an exercise) stay focused on a stand-alone usage, where no
ZODB conflict resolution would help recover from a bug.
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
should fit the needs of code outside transaction
management, such as zeo.memcache .
Regards,
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list
;) .
/ducks
Regards,
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
be inside ZODB ?)
- DemoStorage
- zlibstorage
- ...other Storage interface implementations (NEO, RelStorage, etc)
--
Vincent Pelletier
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org
revisions are deleted
- garbage collection: unreachable objects are deleted
As you noticed, with FileStorage this actually happens by copying every kept
objects and transactions to a new data.fs, and swapping it with original
data.fs - which gets renamed as *.old.
Regards,
--
Vincent Pelletier
ERP5
.
I think this bug was originally noticed by Julien (so CC'ed).
--
Vincent Pelletier
ERP5 - open source ERP/CRM for flexible enterprises
___
For more information about ZODB, see http://zodb.org/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https
API to me (or at least, Connection-level API, not storage-
level).
...at least, we could get it to work in NEO ;) (easier than undo from
performance point of view, but that's another story).
--
Vincent Pelletier
___
For more information about ZODB, see
= []
+for d in self.options.products + Products.__path__:
+if d not in L:
+L.append(d)
+Products.__path__[:] = L
self.setup_default_logging()
self.check_socket()
self.clear_socket()
--
Vincent Pelletier
,
but didn't have the knowledge to implement it back then.
Especially since there's an easy workaround like described above
Indeed.
Regards,
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB
=113734view=markup
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
, I'll open a
bug.
[1]
http://svn.zope.org/zope.publisher/trunk/src/zope/publisher/publish.py?view=markup
Regards,
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB
for higher
level use-casess.
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
(esp. with the achieved/targetted isolation level).
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
://zodb.org/documentation/articles/ZODB2.html
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
Le lundi 24 mai 2010 12:02:40, Wichert Akkerman a écrit :
which prevents the exception overhead.
Right, thought this is a tradeoff question: writing as exception handling is
faster for volatile is present case, but slower for volatile is missing
case.
--
Vincent Pelletier
a single
database doesn't have enough information to perform garbage collection.
Thanks for pointing this package out, I didn't know it.
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev
is held while conflict resolution is
performed.
Oops, I didn't realise that ZEO was postponing Storage.store calls until
tpc_vote call. I now realise that this is required to not interleave stores
from different transactions in underlying storage.
--
Vincent Pelletier
before integration.
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
the overhead.
Why not defining some kind of callbacks in Storage API, which would allow to
plug such mechanisms in a storage rather than wrapping around it ?
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http
-High.Performance.Zope/view
Regards,
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
interested in undoing
transactions modifying context, not transaction done on context (so they
actually want to use the efficient history tab, the one using FileStorage
object version back-pointers).
--
Vincent Pelletier
___
For more information about
.
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zodb-dev
invalidation number will have been long forgotten by Zeo)
- it might slow down transaction to add an exchange at storage join (if there
is none at the moment, which I don't know)
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB
class which would instruct
publisher to retry transaction and another to instruct it to give up (...and
of course abort transaction) as fast as possible.
I have no idea about the needed amount of work.
--
Vincent Pelletier
___
For more information about
transaction using it.
Is there any reason why TM._register is hiding exceptions ?
--
Vincent Pelletier
___
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/
ZODB-Dev mailing list - ZODB-Dev@zope.org
http://mail.zope.org
44 matches
Mail list logo
