Hi all, In addition to adding support for transactions, I'm thinking about clarifying the "to" attribute of the getColumn method. I think that, right now, getColumn simply does nothing (i.e. does not create/modify an attribute) if a database column is null. I'm thinking that, instead, the getColumn tag should actually _remove_ any attribute by that name if the database column was null. That way, if consecutive statements try to write to the same attribute, you can reliably tell whether or not the last statement returned a null by the existence, or lack thereof, of an attribute. - Morgan ===== Morgan Delagrange Britannica.com __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices. http://auctions.yahoo.com/
