April 2001 - Zope-Dev

why is this more efficient
by Tim McLaughlin 23 Apr '01

23 Apr '01

Found this in the constructor for the File Product and I don't understand why it is more efficient. (I want to subclass a File, so this does have some purpose ;-)) Anybody got any ideas? # First, we create the file without data: self._setObject(id, File(id,title,'',content_type, precondition)) # Now we "upload" the data. By doing this in two steps, we # can use a database trick to make the upload more efficient. self._getOb(id).manage_upload(file) ___________________________________________________________ Tim McLaughlin BCSwebservices.net Director, Technical Group 1950 Old Gallows Road tel: (703) 790.8081 x111 Suite 201 tim(a)bcswebservices.net Vienna, VA 22182 www .bcswebservices. net

2 1

Plugable brains changed in 2.3x vs 2.2?
by Brad Clements 23 Apr '01

23 Apr '01

I've been using zope 2.2.2 with a plugable brain that does something like this: class Mybrain: def __init__(self): self.__dict['myvar'] = 'xyzzy' I just moved to the latest 2.3 beta and get an error that "__dict__" doesn't exist. Anyone have a quick pointer for a fix, I have 60 minutes to make this work. thanks Brad Clements, bkc(a)murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com AOL-IM: BKClements

1 1

has_role vs. hasRole
by Stefane Fermigier 23 Apr '01

23 Apr '01

Hi, a developer who's working with me has been bitten by the following fact today, one year after me. There are two methods on objects BasicUser. One is called "has_role" and has the following docstring: """Check to see if a user has a given role or roles.""" The other one is called hasRole, is an alias on another method that's called "allowed" and has the following docstring: """Check whether the user has access to object, assuming that object.__roles__ is the given roles.""" (The Zope Book doesn't say anything on "has_role" (why?) but says about "hasRole": hasRole(object, roles) -- Return a value that is true if the user has the given roles on the given object and return false otherwise.) I understand that those two methods have differents signatures and different uses, but I think that the names are too similar to not induce confusion. S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). http://nuxeo.com/ & http://portalux.com/ & http://aful.org/ "Amazon: we patent the dot in .com"

1 0

RE: [Zope-dev] CoreSessionTracking
by Randall F. Kern 23 Apr '01

23 Apr '01

The documentation is in lib/python/AccessControl/DTML.py :) > From: Chris Withers [mailto:chrisw@nipltd.com] > <dtml-var "_.SecurityGetUser().getUserName()"> as for simplifying _.SecurityGetUser().getUserName(), BasicUser defines __str__ to return getUserName(), so <dtml-var SecurityGetUser> should result in the same output as <dtml-var expr="_.SecurityGetUser().getUserName()"> -Randy

2 1

RE: [Zope-dev] CoreSessionTracking
by Randall F. Kern 23 Apr '01

23 Apr '01

_.SecurityGetUser() -Randy

3 2

Re: [Zope-dev] ZPatterns AttributeProvider question
by cs＠comlounge.net 23 Apr '01

23 Apr '01

Hi! So here's more :) > > def _objectAdding(self,client, > > _tmap={ None:AddedStatus, > > DeletedStatus:ChangedStatus, > > ChangedStatus:AddedStatus > > } > > ): > > t = client._getTokenFor(self) > > s = t.status > > t.status = _tmap.get(s,s) > > > > # we need to do a commit here in order to store the record into > the database! > > # and we need to have it stored as an AttributeFor() of the primary key will > > # return None otherwise (as this also just makes a query). > > client.commitSubtransaction() > > This is broken. Don't do this! commitSubtransaction() is an > application-level operation. Only. If you have to use it inside of > provider-level code or code called from SkinScript, chances are that you > are doing something horribly wrong. You run the risk of causing a > recursive commit operation in the Zope transaction machinery. Don't do this! well, it always looked no-good to me, I just didn't know how to solve my problem. So my problem I was trying to fix was actually the following: - When creating a new object via newItem(), the Rack checks if self.loadAttrib is defined before creating a new one. if loadAttrib is returned by the attribute provider then the Rack assumes it already exists and raises an exception. - My Attribute Provider now does not know if an object exists or not before looking into the database (I tried different ways to check it but somehow they haven't worked). So it does that. If it finds a record with the given id it returns it, if not it returns the default value (which means "does not exist" to the rack). - When adding a new object in my provider it does an insert via an ZSQL method to store it inside the database. This is done in _objectAdded(). Unfortunately this is too late as before this is called, we already need to have it in the database as the request to my primary key will return the default still. So I moved this insert to _objectAdding(). Unfortunately this new record seems not to appear in the database before commit() (dunno why, maybe some new transaction code in ZMySQLDA? haven't checked this). That's why I did a commit() there which then called _objectAdded(). So my problem is basically that I need to know in _AttributeFor() whether this object is already created or not.. I will check now again with asking the status of the client but I think I also tried this before. The best would be to collect all data before _objectAdded() and store it at once and not as it's done now by first creating an empty record and doing the rest via _objectChanged(). But I am open for any other idea :) > > def _SetAttributeFor(self,client,name,value): > > """Set the attribute and return true if successful""" > > # attribs stores the attributes we care about > > if name in self._attribs.keys(): > > client._getCache()[name]=value > > client.__dict__[name]=value; > > client._p_changed = 1 > > return 1 > > return None > > This also looks broken to me. Why are you changing both the cache and the > persistent state? There's no reason to do both. ok, this is old code where I wanted to test some other solution to fix my problem. I will remove the additional line.. (__dict__ might be all I need, it's already a cache if I remember right?!?) > I think you're seriously over-engineering this. I don't see anything that > you're doing here that couldn't be done more easily with SkinScript > statements. If all you want to do is store the data in an SQL database, a > few SkinScript triggers would suffice. Well, as mailed yesterday I know this. I've also done this a lot but was then tired of always typing those paramater lists (for each ZSQL method, for each SkinScript call twice, ...). This is of course always the tradeoff between easy to use plugins which are somehow restricted and the more flexible ones which do need lots of configuration. I would like to have the first one for the day-to-day-stuff and the latter for more advanced operations, like linking specialists together etc. > Now, if you're trying to get a row to be inserted in an SQL database at the > actual time of the newItem() call, there is a trick you can use to do that > from SkinScript also. Do this: > > INITIALIZE OBJECT WITH someAttr1=default1, > someAttr2=default2,...,dummyAttributeName=myInsertQuery(primaryKey=self.id) > > Where myInsertQuery() is an SQL insert query that takes primaryKey as a > parameter, and dummyAttributeName is some attribute name you don't care > about. You should also set any default values for fields that will be > inserted. Your insert query will be called, initializing the row in the > database, and then use something like this: > > WHEN OBJECT ADDED,CHANGED STORE foo,bar,baz USING > UpdateMethod(widget_id=self.id, foo_field=self.foo, wbar=self.bar) > > > To update the data at transaction commit time. Voila. No need to make any > custom attribute providers just to do this. Actually when using SkinScript I never had the need for directly putting the new row into the db, as then I haven't had the loadAttrib problem ;-) > Just to clarify the event sequence that should take place: > > 1. newItem() is called, which fires an _objectCreating() event > > 1.1. The SkinScript INITIALIZE OBJECT statement is triggered by the > _objectCreating() event, and calls myInsertQuery() to insert a row in the > database, with default values for everything but the primary key. Hm, _objectCreating() is a method of which object? Can I define it in some agent or is it a method of the DataSkin or a Rack? I will read more closely about the rest when I get back to programming, so I might mail then again.. (if you don't mind). > Whew. The above is a vastly simplified picture of the whole sequence, > leaving out a lot of things such as how a statement can actually be > responsible for many dataskins at once, the state machine that agents use > to decide which event is considered to have occurred, etc. There aren't any UML diagrams of all this btw? ;-) ok, thanks for the enlightenment! :) cheers, christian -- COM.lounge http://comlounge.net/ communication & design info(a)comlounge.net

1 0

RE: [Zope-dev] CoreSessionTracking
by Adrian Hungate 23 Apr '01

23 Apr '01

Do you mean: from AccessControl import getSecurityManager security = getSecurityManager() user = security.getUser() userName = user.getUserName() ??? Adrian... -----Original Message----- From: Chris Withers [mailto:chrisw@nipltd.com] Sent: Monday, 23 April 2001 16:57 To: Chris McDonough Cc: Magnus Heino (Rivermen); zope-dev(a)zope.org Subject: Re: [Zope-dev] CoreSessionTracking Chris McDonough wrote: > > Alternately (and this will be in the next CST release), add this to the > session data object class (SessionData.SessionData): > > __guarded_setitem__ = __setitem__ OK, that'll teach me to read the whole thread before I post :-) > As far as finding the currently logged in user's name, try this: > > context.REQUEST['AUTHENTICATED_USER'].getUserName() > > This is a deprecated API, however. The new one I can't find at the moment, > though. ;-) When you find out, can you let us know :-S Chris _______________________________________________ Zope-Dev maillist - Zope-Dev(a)zope.org http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )

2 1

ZCatalog waaaagh!
by Chris Withers 23 Apr '01

23 Apr '01

Hi Chris (and anyone else who can help), Hopefully you may be able to save my sanity. Querying a ZCatalog(2.3.1, running update thing made no difference), I'm getting the following error: type: exceptions.TypeError value: len() of unsized object sr = self.searchResults(kw) File "E:\Zope\2379A4~1.1\lib\python\Products\ZCatalog\ZCatalog.py", line 535, in searchResults (REQUEST,used, query_map), kw) File "E:\Zope\2379A4~1.1\lib\python\Products\ZCatalog\Catalog.py", line 651, i n searchResults used=self._indexedSearch(kw, sort_index, r.append, used) File "E:\Zope\2379A4~1.1\lib\python\Products\ZCatalog\Catalog.py", line 558, i n _indexedSearch append((k,LazyMap(self.__getitem__, intset))) File "E:\Zope\2.3.1\lib\python\Products\ZCatalog\Lazy.py", line 205, in __init __ self._len = len(seq) I inserted a print `seq` before that line, and the situations where it barfs, seq is either 461695167 or 0, rather than the list it should be. Has anyone else seen this? Anyone got a cleu what's going on or how I can find out what's going on? cheers, Chris

2 11

SV: [Zope-dev] CoreSessionTracking
by Magnus Heino (Rivermen) 23 Apr '01

23 Apr '01

> In the meantime, use the .set method of the session data > object, e.g. in the > onStart function: > > sdo.set('Username', 'Foobar') > > .. or use an external method. Ok, works now. Thanks. How to I access things like the DTML AUTHENTICATED_USER.getUserName() from a python script? /Magnus

3 2

SV: [Zope-dev] CoreSessionTracking
by Magnus Heino (Rivermen) 23 Apr '01

23 Apr '01

This onStart method... sdo['date'] = context.ZopeTime() ...gives this error: ------ 2001-04-23T14:36:32 PROBLEM(100) Session Tracking session event failed The call to function onStart failed. Traceback: Traceback (innermost last): File /usr/home/magnus/www/Zope-2.3.1-src/lib/python/Products/CoreSessionTracking/ SessionDataManager.py, line 451, in __call__ (Object: ) File /usr/home/magnus/www/Zope-2.3.1-src/lib/python/Shared/DC/Scripts/Bindings.py , line 324, in __call__ (Object: onStart) File /usr/home/magnus/www/Zope-2.3.1-src/lib/python/Shared/DC/Scripts/Bindings.py , line 354, in _bindAndExec (Object: onStart) File /usr/home/magnus/www/Zope-2.3.1-src/lib/python/Products/PythonScripts/Python Script.py, line 336, in _exec (Object: onStart) (Info: ({'script': <PythonScript instance at 87d1b10>, 'context': <Folder instance at 8847358>, 'container': <Folder instance at 8847358>, 'traverse_subpath': []}, ({},), {}, None)) File Script (Python), line 2, in onStart File /usr/home/magnus/www/Zope-2.3.1-src/lib/python/Products/PythonScripts/zbytec odehacks/VSExec.py, line 430, in __setitem__ TypeError: object does not support item assignment

3 2