One entity group per web2py object, lack of list property support, etc. dooms the current implementation to "small" web sites. If db.py has no tables, will the "Web2py also re-evaluates your model definition" overhead vanish? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
- [web2py:31896] app engine data model best practices AndrewLoot
- [web2py:31912] Re: app engine data model best practices Robin B
- [web2py:31922] Re: app engine data model best practice... AndrewLoot
- [web2py:31929] Re: app engine data model best prac... Robin B
- [web2py:31931] Re: app engine data model best ... mdipierro
- [web2py:31944] Re: app engine data model ... Robin B
- [web2py:31958] Re: app engine data mo... notcourage
- [web2py:31965] Re: app engine dat... AndrewLoot
- [web2py:31967] Re: app engine dat... Richard
- [web2py:31969] Re: app engine dat... Robin B
- [web2py:31982] Re: app engine dat... dlypka
- [web2py:31985] Re: app engine dat... AndrewLoot

