On Wed, Sep 17, 2003 at 07:46:58AM -0400, Gordon McMillan wrote:
> On 17 Sep 2003 at 1:25, Nicholas Riley wrote:
>
> [...]
>
> > I'm working under the assumption that, given a database, you'd
> > prefer it to generate an error rather than discard data.
>
> Not at all. When working with GUI forms, I often use a form dict
> which may well have extra state I don't want persisted.
This addresses one of the three cases I mentioned (unfortunately the
one I've implemented; oh well). What about the others -
view.append(1) and view.append('abcdefg') (where you have fewer than 7
properties)?
> You'll realize you're discarding data soon enough, and adding
> columns is incredibly easy. I, on the other hand, would have to
> add a bunch of code just to avoid a paternalistic error. If I liked
> doing that, I'd be using Java <wink>.
Understood about Java; that's why I'm using Python in the first place
;-) Still, I am trying to approximate the level of error checking of
Python's builtins. ZODB, which I've used in the past, has a different
mechanism for specifying which attributes of an object are persisted,
beyond simply ignoring unspecified attributes.
> BTW, doing type checking code that works across Python
> versions has gotten very difficult. Mk4py still works with
> Python 1.5.2, and at least a couple of us have virtual hosts
> still running 1.5.2.
I didn't realize I needed to test that far back. What a mess. It'd
be nice if this minimum requirement were documented somewhere more
obvious.
What Python versions do you test with? I know I at least need to do
2.2 and 2.3 to test for varying Unicode and integer handling, but is
1.5.2 adequate in addition or do I need to test more intermediate
versions such as 2.0, 2.1, etc.?
--
=Nicholas Riley <[EMAIL PROTECTED]> | <http://www.uiuc.edu/ph/www/njriley>
_______________________________________________
metakit mailing list - [EMAIL PROTECTED]
http://www.equi4.com/mailman/listinfo/metakit
