My advice would be to start with the database back end you will ultimately use.
With 10,000 tables you would have to explore a way to avoid running the model files with every request. There are posts in this forum that explain how to do it. On Friday, December 28, 2012 10:38:25 AM UTC-5, Alex Glaros wrote: > > Can web2py be used for highly complex relational databases for large > fiscal projects? Example: California's Fi$cal project - > http://www.fiscal.ca.gov/<http://www.linkedin.com/redirect?url=http%3A%2F%2Fwww%2Efiscal%2Eca%2Egov%2F&urlhash=DBJm&_t=tracking_anet> > - with roughly 10,000 tables and many complex joins. > > What components of web2py would start to get slow or not work well when > having so many tables? > > If web2py would instead be better used to prototype the Fi$cal system, > what would be good production-version candidates to migrate to? Pure Python > using sqlAlchemy? Java? Anything that would make migration easier such as > Python-based frameworks? > > Thanks, > > Alex Glaros --
