Ah, well by "recently" I'm guessing you mean within the last 6 months. I just did an update and works now :)
Thanks for the additional advice - I will have the scheduled task return a TABLE(). Now I need to take a closer look at your w2p_tvseries code to get the PeriodicalUpdater to work. -Andre On Thursday, May 12, 2016 at 3:32:12 PM UTC-4, Niphlod wrote: > > this has been solved recently (the result couldn't be larger than 64k on > most platforms). Right now it has no limitations, although its surely > finite. > Please do keep in mind that (on top of your task being forced to pass > around big chunks of data) result is always json string. > Whenever you need to save and load a result, you convert back and forth > to/from json. > > If your "thing to do" its in the form of a series of zillions of rows that > needs to stored properly, you'd waste far less "energy" just making your > scheduled task saving the result in the "final" table rather than returning > the result and then having another piece that fetches the result from the > scheduled task and translates the result to the table. > > On Thursday, May 12, 2016 at 5:44:53 PM UTC+2, Alfonso Serra wrote: >> >> A Task's run_output and run_result fields types are mapped to LONGTEXT if >> you are using mysql, this is 4gb storage capacity. Python strings should be >> around 3Gb depending on your system's ram amount. >> >> >> -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
