December 2000 - Zope-Dev

ZPatterns: persistant objects hold DataSkin-Items -> KeyError: _v_dm_
by Ulrich Eck 14 Dec '00

14 Dec '00

hi out there, i use zpatterns/specialists for a Network-Documentation Tool. I'm writing a Product which controls the relations between specialists and manages multible actions (edit/new/delete) for ZPatterns DataSkinObjects (DSO). I have a Product-Instance of ZTWM (ZTransactionWorkflowManager) in my application root which is a Folder by itself and holds as folder-objects its 'Transactions' (in this case a Transaction starts at the first edit-action and lasts til the last submit of a form with valid entries - e.g finish transaction.) It behaves like a Wizard (PTK) with next/back/cancel/finish buttons and reads out the DataSkinPropertysheet for creating the edit/new forms on the fly. One can also define relations between the specialists an they are used to edit Foreign Keys. small painting here: \application-root --\<Person> (specialist for persons) --\<Komponent> (specialist for komponents) --\<ZTWM> (my TransactionWorkflowMangager - Folder) ---- \<1> (first transaction -Folder) -------\<1> (first transaction object - Folder) --------| ds_object (attribute which references the DSO) --------| more info on the current Transaction object -------\<2> (second Transaction object) --------| ds_object (attribute which references the DSO) --------| more info on the current Transaction object ----\<2> (second Transaction) ... so far about how it should work .. For each TransactionObject (TO) I save the Object I retrieved with "specialist.getItem(id) == DataSkinObject(DSO)" as attribute "ds_object" to the TransactionObject. After I restarted Zope and want to replay/finish a transaction, i get an KeyError, Value _v_dm_ the prefix _v_ stands for not pickeable (afaik) dm for datamanager ?!? ok .. i put a TO in the Transaction, get the actual DSO, call the transactionmanagers editor function and a form with correct values is displayed, i can edit this form and call the DSO manage_changeProperties method from the transactionmanager. when i don't finish a transaction and restart zope i still have my transactions with proper values saved in my TransactionManager - except the property "ds_object" wich was assigned to the DSO at TO-creation when i try to set/get an attribute i get the KeyError of "_v_dm " ... I can deal arround that if i reget the DSO from the specialist in every function which deals with DSO's. is there a better way to a) tell my TransactionManager that my attribute "ds_object" is not pickeable (e.g. call it _v_ds_object) and how to know if zope is restarted ?!?!? or b) store this object persistantly in my TO without showing it in the folder-structure but behave like a DSO set/get attributes through Skinscripts hope that i described clearly enough where my problem is ... thanks for your reply Ulrich Eck net-labs

3 6

python 2.0, windows and zope
by Andy McKay 14 Dec '00

14 Dec '00

Has anyone got python 2.0 working with Zope on windows? Just curious if anyone has any pointers before I start done this (potentially) painful path... -- Andy McKay, Developer. ActiveState.

4 6

Re: [Zope-dev] Linux Zope <-> Win2K SQL Server?
by Anthony Baxter 14 Dec '00

14 Dec '00

Use the Sybase client libraries, with ZSybaseDA. We do that here, and it works fine (but not for much longer, byebye sqlserver...) Or FreeTDS, but I don't think it's thread-safe, so you'll need to use a Thunked adaptor. >>> "Neil K" wrote > > I'm still trying to figure out what the missing pieces are... if anyone else > has gotten a Linux Zope talking to a Win2K SQL Server 2000, I would > appreciate some guidance. > > It seems I would have to write my own Product from scratch to do this, no > matter what. None of the ODBC Products seem to be available for Unix, and > ODBC from Unix <-> Windows will require additional software like EasySoft's > ODBC Bridge anyway. Or I could just not use ODBC at all and make some > Product customized to MS SQL Server. > > Some may suggest using ActiveState's Perl Methods for Zope and DBD::Proxy. > :) It's a possibility, but I'd like to see if more conventional solutions > exist. > > -- > Neil Kandalgaonkar, ActiveState > > > > _______________________________________________ > 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 ) > -- Anthony Baxter <anthony(a)interlink.com.au> It's never too late to have a happy childhood.

2 1

Converters.py field2date() and :ignore_empty
by Brad Clements 14 Dec '00

14 Dec '00

If I have ignore_empty set in a variable name of type date, field2date() fails if the returned value is truly empty. I think field2date() should return None rather than trying to call DateTime with an empty string. I keep making this patch to each Zope release, but would like to talk about a more permanant and "correct" solution. What do others think? 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

3 2

Adding and setting properties from a virtual Specialist
by Itai Tavor 14 Dec '00

14 Dec '00

Hi, I have a Specialist ('OrderingEntities') which creates virtual objects, mapped to existing objects (using ZClass 'Employee') in another Specialist ('Employees'). I want OrderingEntities to add and modify a property 'current_order_id' on the Employee objects. I can get the virtual object to access properties from the real object, but I can't figure out how to implement the property add/change. To make things simpler, I added the property current_order_id to the Employee class, so I can test just modifying this property, leaving creating it for later. OrderingEntities has an employeeRack, set to use the Employee class and to load by accessing attribute current_order_id. The Rack has this SkinScript: WITH Employees.getItem(self.id) COMPUTE original_object=RESULT or NOT_FOUND WITH self.original_object COMPUTE current_order_id WHEN OBJECT ADDED,CHANGED STORE current_order_id USING self.original_object.manage_changeProperties(current_order_id=self.current_order_id) Doing <dtml-var "OrderingEntities.getItem(some_id).current_order_id)"> shows me the value of current_order_id of the Employee object some_id. But I can't figure out how to change the property so it get changed in the Employee object. <dtml-call "OrderingEntities.getItem(some_id).manage_changeProperties(current_order_id='123')"> does nothing, it doesn't even trigger the WHEN OBJECT CHANGED line (not that I really expected it to work... this object is virtual, how can I call changeProperties on it?) Other than figuring out how to get the change to work, I two more problems: -Eventually the OrderingEntities Specialist will have several Racks mapping to several other Specialists, so it will end up returning different classes. Should I instead create a new ZClass with just the current_order_id property and use this class in all the virtual Racks? - How do I add a property to the original object from the virtual object (assuming I did not add it manually to the Employee class)? Do I call self.original_object.manage_addProperty(...) from the SkinScript? TIA -- Itai Tavor "Je sautille, donc je suis." C3Works itai(a)c3works.com - Kermit the Frog "If you haven't got your health, you haven't got anything"

2 3

Announcing ZODB-Corba code release
by John D. Heintz 13 Dec '00

13 Dec '00

Here is the first release of code that exposes a ZODB database through CORBA (omniORB). The code is functioning, the docs are sparse, and it should work on your machines. ;-) I am only going to be in town for the next two days, then I will be unavailable until Jan 1. See http://www.zope.org/Members/jheintz/ZODB_CORBA_Connection to download the code. It's not perfect, but it works for me. Enjoy, John -- .. . . . . . . . . . . . . . . . . . . . . . . . John D. Heintz | Senior Engineer 1016 La Posada Dr. | Suite 240 | Austin TX 78752 T 512.633.1198 | jheintz(a)isogen.com w w w . d a t a c h a n n e l . c o m _______________________________________________ Bug reports, feature requests, etc. go in the ZEO Tracker: http://www.zope.org/Products/ZEO/Tracker Conversations etc. can take place in the Wiki: http://www.zope.org/Products/ZEO/Wiki Zope-ZEO maillist - Zope-ZEO(a)zope.org http://lists.zope.org/mailman/listinfo/zope-zeo

1 0

zPoPyDA and DB Transactions
by Casey Duncan 13 Dec '00

13 Dec '00

I had been using Postgres with the zPyGreSQLDA and recently switched to zPoPyDA for a new project. I noticed that zPoPyDA does not seem to implicitly wrap each zSQL method in a database transaction as zPyGreSQLDA did. Reading the code for zPoPyDA seems to confirm this. Is this behavior by design or a bug or am I missing something? -- | Casey Duncan | Kaivo, Inc. | cduncan(a)kaivo.com `------------------>

1 0

ANNOUNCE: Zope 2.3.0 alpha 1 released...
by Brian Lloyd 13 Dec '00

13 Dec '00

Hello all, As promised, Zope 2.3.0 alpha 1 is now available. You can download it from Zope.org: http://www.zope.org/Products/Zope/2.3.0a1/ This release contains a number of important new usability features, and also marks the first release where a substantial amount of the work done happened in the Fishbowl on dev.zope.org. Some highlights of this release: - Python Scripts are now part of the Zope core. Big whopping kudos to Evan Simpson for all of the work he has put into this! Having Python Scripts in the core will allow people to much more easily separate logic and presentation (and get that logic out of DTML!) More information and prototype documentation for Python Scripts can be found in the dev.zope.org project: http://dev.zope.org/Wikis/DevSite/Projects/PythonMethods - The process of creating an initial user at install time has finally been fixed. Before you had to create a superuser, login as the superuser, create a normal manager, logout, then log back in as the normal manager. This was obtuse and caused big problems for newbies who would log in as the superuser and start trying to work immediately (leading to errors since the superuser cannot own objects). This process is now much more sane. Now, at install time a default initial manager (not a superuser) is created. The superuser has been renamed to the "emergency user" and is not even created by default. If you ever have a need to log in as the emergency user, you can use zpasswd.py to create it. - The new security assertion support has been checked in. For more information and an updated version of the "Zope security for developers" guide see the project on dev.zope.org: http://dev.zope.org/Wikis/DevSite/Projects/DeclarativeSecurity - Added new getId() method to SimpleItem.Item. This should now be used instead of referencing 'object.id' directly, as it is guaranteed to always be a method and to always return the right thing regardless of how the id of the object is stored internally. This relieves DTML writers of the contortions they previously had to go through to handle varying cases of 'id' being a method or an attribute. - Improved Ownership controls. Now you simply choose whether or not to take ownership of sub-objects when taking ownership. Implementation details about whether ownership is implicit or explicit are no longer forced on the user. - Unit testing infrastructure for the Zope core. PyUnit has been checked in, and a utility has been added that will allow us to incrementally begin accumulating (and running) test suites. The new testrunner.py in the utilities directory is a basic utility for running PyUnit based unit tests. It can be used to run all tests found in the Zope tree, all test suites in a given directory or in specific files. The testrunner will be used to ensure that all checked in tests pass before releases are made. For more information, see the docstring of the actual testrunner.py module. For more information on what is new in this release, see the CHANGES.txt and HISTORY.txt files for the release: http://www.zope.org/Products/Zope/2.3.0a1/CHANGES.txt http://www.zope.org/Products/Zope/2.3.0a1/HISTORY.txt *Please note* that we do not build binary distributions for alpha releases - the alpha is available as a source release only. When we move into the beta period for 2.3, we will build and distribute binary releases. Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

2 2

Python 2 (Zope Unicode) support for 2.2.4
by Steve Alexander 12 Dec '00

12 Dec '00

Hi Folks, I've modified Toby Dickenson's patch to let Zope work with Python 2 so that it patches against Zope 2.2.4. http://www.zope.org/Members/stevea/unicode_for_224.patch.gz Toby's page about using unicode and Python 2 with Zope is here: http://www.zope.org/Members/htrd/wstring -- Steve Alexander Software Engineer Cat-Box limited http://www.cat-box.net

1 0

Pending bugs in collector - how do I send this patch?
by Brad Clements 12 Dec '00

12 Dec '00

I have found a bug in ZSQL methods that is describe by this collector item: http://classic.zope.org:8080/Collector/718/view This item was posted over a year ago! The bug is still in the program, so I'm guessing that DC folks are too busy to get to this. The collector item described above describes a weak work-around because the submitter didn't understand how this exception can occur.. Here's how it happens.. If a query is executed twice, the second time beyond the cache time limit. Then the query string is stored in tcache{} twice (two different times) but in cache{} only once. Eventually the cache reaches it's maximum size and entries are expired in reverse time order. The earlier tcache{} entry is encountered and the query in cache{} is deleted. Eventually the later query is also deleted from tcache{}, but the query no longer exists in cache{} and a KeyError is raised. Here's the fix I'm applying. I'm only deleting the cache{} entry if it's time matches the tcache{} entry that is about to be deleted. I couldn't figure out how to post a patch for a pending collector item. Also didn't want to duplicate the pending bug report either. -- lib/python/Shared/DC/DA.py line 392 or so while keys and (len(keys) > max_cache or keys[-1] < t): key=keys[-1] q=tcache[key] del tcache[key] if int(cache[q][0]) == key: del cache[q] del keys[-1] My change is: if int(cache[q][0]) == key: del cache[q] 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

2 1