- Zope-Dev - Zope lists

Broken objects
by Victor Safronovich 29 Sep '05

29 Sep '05

Hello zope-dev! http://www.zope.org/Collectors/Zope/1911 I try to migrate my old database from zope 2.6.1. I have Broken objects, but it is impossible to get its state in Zope 2.8. In Zope 2.6 Broken objects have states, what i uses to migrate its. I think this is because DB.classFactory is overrided to use OFS.Uninstalled.BrokenClass, which is bad persistent class. the __dict__ of all my Broken objects equals to {'_p_changed':None}. my_object._p_mtime does not load it`s state. -- Best regards, Victor Safronovich NauMen.NauDoc.SoftwareDeveloper http://www.naumen.ru

3 9

Re: "'Savepoints unsupported' on uploading files into zope"
by Chris Withers 29 Sep '05

29 Sep '05

lavrinenko wrote: >>>RDB-based user folder? ZSQL methods being used somewhere? > > Yes, exUserFolder with MySQL Authentication Source Try SimpleUserFolder ;-) Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

"'Savepoints unsupported' on uploading files into zope"
by Chris Withers 29 Sep '05

29 Sep '05

lavrinenko wrote: > I suspect the bug is in Image.py, and the whole database adapters thing is a > red herring. > > Either that, or Shared.ZRDB has become geb0rken in 2.8 when it comes to > savepoints. ..or, as another possibility, both the DA's these errors have been reported with haven't been updated to support savepoints, which would make the error message more sensible. Although why the DAs are becoming involved when you're just doing stuff with images is beyond me... RDB-based user folder? ZSQL methods being used somewhere? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Re: [Zope-Checkins] SVN: Zope/trunk/lib/python/DocumentTemplate/cDocumentTemplate.c Fix incorrect docstring.
by Chris Withers 28 Sep '05

28 Sep '05

Nah, I refer you instead to the docstring at the top of that file which says it's no longer used and is for reference only. It's already out of synch in implementation, so I don't see any point in fixing this one detail... cheers, Chris Victor Safronovich wrote: > Hello Chris Withers, > > Wednesday, September 28, 2005, 6:48:20 PM, you wrote: > > CW> Log message for revision 38664: > CW> Fix incorrect docstring. > > CW> Changed: > CW> U Zope/trunk/lib/python/DocumentTemplate/cDocumentTemplate.c > > CW> -=- > CW> Modified: Zope/trunk/lib/python/DocumentTemplate/cDocumentTemplate.c > CW> =================================================================== > CW> --- > CW> Zope/trunk/lib/python/DocumentTemplate/cDocumentTemplate.c 2005-09-28 > CW> 11:19:50 UTC (rev 38663) > CW> +++ > CW> Zope/trunk/lib/python/DocumentTemplate/cDocumentTemplate.c 2005-09-28 > CW> 12:48:20 UTC (rev 38664) > CW> @@ -420,10 +420,11 @@ > CW> {"_pop", (PyCFunction) MM_pop, 0, > CW> "_pop() -- Remove and return the last data source added"}, > CW> {"getitem", (PyCFunction) MM_get, METH_VARARGS, > CW> - "getitem(key[,call]) -- Get a value\n\n" > CW> - "Normally, callable objects that can be called without arguments are\n" > CW> - "called during retrieval. This can be suppressed by providing a\n" > CW> - "second argument that is false.\n" > CW> + "getitem(key[,call]) -- Get a value from the MultiDict\n\n" > CW> + "If call is true, callable objects that can be called without arguments are\n" > CW> + "called during retrieval.\n" > CW> + "If call is false, the object will be returns without any attempt to call it.\n" > CW> + "If not specified, call is false by default.\n" > please change pDocumentTemplate.py, where _call_ is true by default. > -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 2

Re: SVN: Zope/branches/Zope-2_8-branch/ - Collector #1879: applied patch by Dieter Maurer to fix a bug in
by Florent Guillaume 27 Sep '05

27 Sep '05

This is the kind of thing that would *really* benefit from having unit tests... Florent Andreas Jung <andreas(a)andreas-jung.com> wrote: > Log message for revision 38586: > - Collector #1879: applied patch by Dieter Maurer to fix a bug in > ac_aquire() ignoring the default argument > > > Changed: > U Zope/branches/Zope-2_8-branch/doc/CHANGES.txt > U Zope/branches/Zope-2_8-branch/lib/python/Acquisition/_Acquisition.c > > -=- > Modified: Zope/branches/Zope-2_8-branch/doc/CHANGES.txt > =================================================================== > --- Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2005-09-24 12:01:37 UTC > (rev 38585) > +++ Zope/branches/Zope-2_8-branch/doc/CHANGES.txt 2005-09-24 12:10:07 UTC > (rev 38586) > @@ -31,6 +31,9 @@ > > Bugs Fixed > > + - Collector #1879: applied patch by Dieter Maurer to fix a bug in > + ac_aquire() ignoring the default argument > + > - Collector #1864, #1906: fixed header normalization in appendHeader() > > - Collector #1899: fixed migration issue when using export/import for > > Modified: Zope/branches/Zope-2_8-branch/lib/python/Acquisition/_Acquisition.c > =================================================================== > --- Zope/branches/Zope-2_8-branch/lib/python/Acquisition/_Acquisition.c > 2005-09-24 12:01:37 UTC (rev 38585) > +++ Zope/branches/Zope-2_8-branch/lib/python/Acquisition/_Acquisition.c > 2005-09-24 12:10:07 UTC (rev 38586) > @@ -1059,6 +1059,7 @@ > PyObject *expl=0, *defalt=0; > int explicit=1; > int containment=0; > + PyObject *result; /* DM 2005-08-25: argument "default" ignored */ > > UNLESS (PyArg_ParseTupleAndKeywords( > args, kw, "O|OOOOi", acquire_args+1, > @@ -1070,12 +1071,34 @@ > > if (filter==Py_None) filter=0; > > + /* DM 2005-08-25: argument "default" ignored -- fix it! */ > +# if 0 > return Wrapper_findattr(self,name,filter,extra,OBJECT(self),1, > explicit || > self->ob_type==(PyTypeObject*)&Wrappertype, > explicit, containment); > +# else > + result = Wrapper_findattr(self,name,filter,extra,OBJECT(self),1, > + explicit || > + self->ob_type==(PyTypeObject*)&Wrappertype, > + explicit, containment); > + if (result == NULL && defalt != NULL) { > + /* as "Python/bltinmodule.c:builtin_getattr" turn > + only 'AttributeError' into a default value, such > + that e.g. "ConflictError" and errors raised by the filter > + are not mapped to the default value. > + */ > + if (PyErr_ExceptionMatches(PyExc_AttributeError)) { > + PyErr_Clear(); > + Py_INCREF(defalt); > + result = defalt; > + } > + } > + return result; > +# endif > } > > + > static PyObject * > Wrapper_inContextOf(Wrapper *self, PyObject *args) > { -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

3 2

inheritedAttribute -> super
by Florent Guillaume 27 Sep '05

27 Sep '05

Is there any problem if I change current Zope 2 trunk uses of inheritedAttribute into calls to super ? Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of R&D +33 1 40 33 71 59 http://nuxeo.com fg(a)nuxeo.com

1 0

RE: [Zope-dev] Re: Z SQL Caching
by Dale Hirt 26 Sep '05

26 Sep '05

Thank you, Martijn. That makes it very clear. :) -----Original Message----- From: zope-dev-bounces(a)zope.org [mailto:zope-dev-bounces@zope.org]On Behalf Of Martijn Pieters Sent: Monday, September 26, 2005 11:49 AM To: zope-dev(a)zope.org Subject: [Zope-dev] Re: Z SQL Caching Dale Hirt wrote: > I have a Z SQL method that is currently returning around 25000 rows. > Is there a way to see if it is pulling that data from the cache or is > doing a refresh? > > Alternatively, and maybe this will answer the first question, the Z SQL > method is run essentially twice, each time with different parameters. > Does it cache each instance, or does it cache the first, then when it's > run again with different parameters, kill the cache and re-run > everything? A ZSQLMethod cache (if configured with a cache duration greater than 0) is keyed on the rendered SQL. So, if different parameters lead to a different SQL query to be sent to the database, then a different key is used. Caches are kept for the duration of the configured cache duration, and a given cache key will not influence earlier caches of different keys. The SQL is taken quite literally here. If you use the following template: SELECT * FROM foo WHERE <dtml-sqltest bar type="nb"> Then different values for 'bar' will result in different SQL queries and thus different cache keys. If the same method is called with the same value for 'bar' within the cache duration, an earlier cached result will be returned instead of querying the database. Another value for 'bar' in between those calls will not kill the cache. Martijn Pieters _______________________________________________ Zope-Dev maillist - Zope-Dev(a)zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )

1 0

Z SQL Caching
by Dale Hirt 26 Sep '05

26 Sep '05

Hi all, I have a Z SQL method that is currently returning around 25000 rows. Is there a way to see if it is pulling that data from the cache or is doing a refresh? Alternatively, and maybe this will answer the first question, the Z SQL method is run essentially twice, each time with different parameters. Does it cache each instance, or does it cache the first, then when it's run again with different parameters, kill the cache and re-run everything? Thanks, Dale Hirt

2 1

[Fwd: Re: [Zope-dev] Problems adding many objects]
by Morten W. Petersen 26 Sep '05

26 Sep '05

Oops, one for the list as well. -------- Original Message -------- Subject: Re: [Zope-dev] Problems adding many objects Date: Mon, 26 Sep 2005 13:34:50 +0200 From: Morten W. Petersen <morten(a)nidelven-it.no> To: Chris McDonough <chrism(a)plope.com> References: <4336AF98.3030606(a)nidelven-it.no> <249B923B-2427-4A01-B656-56300CC7EE88(a)plope.com> <4337D9A8.70107(a)nidelven-it.no> <5806920C-3A04-42EE-A2D5-487F630A10CB(a)plope.com> > It doesn't say "returning issue, None"? My guess is that the if > request is not none branch is called and it goes that way. But there's > no way to know for sure without running it. It says 'returning issue <issue at xxxxx>' > This is a good place to use the Python debugger... as the first line > of this method, insert "import pdb; pdb.set_trace()", then start up > Zope in the foreground (runzope or zopectl fg), then cause the method > to be invoked through a browser. > > On the console you will see a pdb prompt. You can step through the > code by using "n". To print the value of a variable type "p > <variablename>", to step in to a function call press "s". When you're > finished, press "c" to continue or "q" to quit. This will be the > fastest way to see what's happening in this method. Yep, I'll have a go at this later. Thanks for describing the debug process. :) -Morten -- Regards, Morten Tlf: +47 45 44 00 69 Blog: http://www.blogologue.com

1 0

Problems adding many objects
by Morten W. Petersen 26 Sep '05

26 Sep '05

Hi, I've created a script that imports XML into the ZODB, using regular TTW methods - and all is fine, except for when I import large files, with many objects. After about 288 objects, the import fails when the method that adds an object in the ZODB returns None, instead of the object it added. From what I can tell, the added object is not None before it is returned, but the name object, set via the expression object = self.manage_add_issue(...) is None. So it looks like somewhere between 'return issue_' in manage_add_issue and the expression above, the object is lost. Any ideas what could be happening here? I've managed to work around it for now, but it is interesting nonetheless. Regards, Morten

2 3