A) Bring home the bacon ! B) Every time unless you set check_reserve to None. In production you would have check_reserve to None.
C) It should be a union, and that is exactly what its documentation I added says. But we can't do a union until we actually create database specific keywords!!!! until then ALL will have to suffice. -Thadeus On Wed, Feb 3, 2010 at 12:27 PM, Jonathan Lundell <jlund...@pobox.com> wrote: > On Feb 3, 2010, at 9:43 AM, Thadeus Burgess wrote: > >> Ok take a look at the following proposed changes > > I'll try to look at it later today; I'm off to work now. > > Is the check made every time, or only when a table is actually being created > (or migrated)? The latter should be adequate, at least by default, and would > have less impact on performance. > > A side thought: the lists probably ought to be frozensets, not arrays, for > performance. And KEYWORDS_ALL ought to be a union (calculated once) of the > other sets. > > -- > You received this message because you are subscribed to the Google Groups > "web2py-users" group. > To post to this group, send email to web...@googlegroups.com. > To unsubscribe from this group, send email to > web2py+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/web2py?hl=en. > > -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
