On Fri, Jan 22, 2010 at 07:37:57AM -0800, Christopher Lee wrote: > Here is the best solution I could think of: > > - abandon automatic class switching in favor of explicit error messages and > class names. We could provide both caching and non-caching versions of > SQLSequence). If you tried to supply a non-caching itemClass to a caching > database class, you'd get a clear error message telling you this will not > work, and what you must do instead.
+1 --titus -- C. Titus Brown, c...@msu.edu -- You received this message because you are subscribed to the Google Groups "pygr-dev" group. To post to this group, send email to pygr-...@googlegroups.com. To unsubscribe from this group, send email to pygr-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/pygr-dev?hl=en.
