> > Suppose I am new to web2py, but not a newbie to programming and python. I > have a big database and I want to publish things out of it with a nice > framework. I know that accessing the db is critical. I heard web2py is > easy to use.
> I do a simple test. I want to know if there are more than one record of > the kind I am looking for: > > len(db(db.long_table.value=='Am I the only one here?').select( > db.long_table.id, limitby(0,2))) > > I expect it faster than count() on a really big table. Result slow as > hell. Consequence is ... ok I will use a better framework and I will post > somewhere that web2py is nice, but slow, not for serious projects. > Perhaps the default for a standard select should not be to automatically add an orderby, but the context of this thread was pagination within the grid. Do you suggest an alternative in that case that would be faster? Anthony -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
