[web2py] Re: memory leak - model remains in memory after requests

n Monday, February 6, 2017 at 12:17:03 PM UTC-8, Anthony wrote: > > On Friday, February 3, 2017 at 4:05:55 PM UTC-5, MarkEdson AtWork wrote: >> >> I found a similar issue with a db.py module with code like this in it... >> >> from gluon.packages.dal.pydal import DA

[web2py] Re: Deploy with postgresql

If the code that reads AppConfig can't handle whitespace then this bug should definitely be fixed! This type of bug can be very difficult to find because it is so esoteric. On Sunday, February 5, 2017 at 12:26:51 AM UTC-8, Ben Lawrence wrote: > > ok, my dumbness > the AppConfig module doesn't lik

[web2py] Re: memory leak - model remains in memory after requests

I should also mention that I recently updated my code to use multiple controllers. On Monday, February 6, 2017 at 7:53:20 AM UTC-8, MarkEdson AtWork wrote: > > Update, > I ran the sample code I placed in this post over the weekend and it ended > up consuming 1.8GB before py

[web2py] Re: SQLite lock (using DAL in a module)

Also consider that every time any http request is made that all of your modules will be loaded. It may be helpful to use cache.ram to store your database connection so you can re-use it rather than creating a new connection to the database on each request. something like... self.dal_db = cache

[web2py] Re: memory leak - model remains in memory after requests

Update, I ran the sample code I placed in this post over the weekend and it ended up consuming 1.8GB before python stopped functioning. I am running pyDAL (17.1) with a stable web2py release. Is this the built-in Rocket server issue I have run into? On Friday, December 24, 2010 at 4:16:24 PM UTC

[web2py] Re: memory leak - model remains in memory after requests

I found a similar issue with a db.py module with code like this in it... from gluon.packages.dal.pydal import DAL, Field db = DAL("sqlite://storage.sqlite") db.define_table( "test", Field("myid", default=DEFAULT_VALUE, length=15), Field("name", default=DEFAULT_VALUE

[web2py] how to turn off caching for ajax() function calls.

I am trying to update the val() in table data elements on a page. The call updates the text but the updates do not display in the browser. If I inspect the element the old text is still there but when I refresh the page the new text shows up. This behaves as though the initial values returned

[web2py] web2py interprets function name as property

I have a need to stop a thread on the server from web2py. The thread is running and I've stored the thread id so I can retrieve it when I want to abort. The abort code will look something like this: for tid, tobj in threading._active.items(): if tid == stored_thread_id: