some PyDO questions

Hi,

I'm currently looking at using PyDO for some web applications in 
combination with CherryPy and Oracle 9. So far I'm mostly happy, but I 
have a few questions:

1) Is it planned to include some sort of mapping functionality, to 
customize how PyDO object's attributes are mapped to DB fields? This could 
be pretty useful, as our DB structure and the field names are still 
changing from time to time, and it's somewhat tedious to update all 
scripts that use the respective attributes when their names change. I have 
a few ideas about how to provide this myself - either by extending the 
PyDO class and plugging in the mapping in the getSome/getUnique/update/... 
methods, or by changing the PyDO package directly. I'm not too sure yet 
what the best way is though, and it may be pointless to try this if it's 
planned anyway.

2) I noticed that DB fields aren't provided as attributes in PyDO classes, 
only as dictionary entries. While this was easy to workaround (again by 
providing a simple subclass of PyDO that extends the getSome and getUnique 
methods and deriving all model classes from that class), I'm wondering if 
this is a known bug? I'm using Python 2.4.1, cx_Oracle 4.1 and Oracle 9.2 
on a Windows XP machine at the moment.

Cheers, Michael


-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click