well id just call it "InlineDefault" then... On Aug 31, 2006, at 4:19 PM, Jonathan Ellis wrote:
> On 8/29/06, Michael Bayer <[EMAIL PROTECTED]> wrote: >> FYI ive been thinking of adding another layer to "default", where a >> default-producing SQL query or function would be embedded at runtime >> into the INSERT or UPDATE statement's argument clause. This would be >> in contrast to PassiveDefault as it is currently, which only defines >> a "DEFAULT" on a column definition, and ColumnDefault, which even if >> it references a SQL statement, will "pre-execute" the statement >> outside of the actual insert/update. this would allow onupdate >> defaults to fire inline as well as allowing a wider variety of >> oninsert defaults. >> >> So i was thinking of maybe calling it PassiveDefault(something, >> inline=True). although its not entirely "passive" (also the >> "passive" name in general kind of sucks since it doesnt describe >> itself well). any suggestions ? > > Why not make it a subclass of PassiveDefault, or the new default and > PD both subclass "RefetchingDefault"? I prefer to avoid using flags > to indicate behavioral differences when possible. > > -- > Jonathan Ellis > http://spyced.blogspot.com ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Sqlalchemy-users mailing list Sqlalchemy-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sqlalchemy-users
