I've had to run a few 'maintenance' routines on one of my apps :
- we changed a few db fields
- we needed to clear the cache
- the functions that created some db field data were updated, so
everything needed to be tested for compliance and possibly regenerated
i couldn't figure out a good way to handle this .
- with an independent script , i'd lose a lot of the functionality
tied to the app/pyramid
- using the commandline / shell for pyramid , i couldn't figure out
how to run everything with a request object ( as many functions are
tied to that )
so i've ended up creating a few views, lock them down, and then turn
them off after I run them.
nothing has caused a timeout, yet, but i'd like a better option. can
someone point me in the right direction ?
> I've had to run a few 'maintenance' routines on one of my apps :
> - we changed a few db fields
> - we needed to clear the cache
> - the functions that created some db field data were updated, so
> everything needed to be tested for compliance and possibly regenerated
> i couldn't figure out a good way to handle this .
> - with an independent script , i'd lose a lot of the functionality
> tied to the app/pyramid
> - using the commandline / shell for pyramid , i couldn't figure out
> how to run everything with a request object ( as many functions are
> tied to that )
> so i've ended up creating a few views, lock them down, and then turn
> them off after I run them.
> nothing has caused a timeout, yet, but i'd like a better option. can
> someone point me in the right direction ?
> --
> You received this message because you are subscribed to the Google Groups
> "pylons-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pylons-discuss+unsubscribe@googlegroups.com.
> To post to this group, send email to pylons-discuss@googlegroups.com.
> Visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
Jonathan Vanasco wrote:
> I've had to run a few 'maintenance' routines on one of my apps : - we
> changed a few db fields - we needed to clear the cache - the
> functions that created some db field data were updated, so everything
> needed to be tested for compliance and possibly regenerated
> i couldn't figure out a good way to handle this . - with an
> independent script , i'd lose a lot of the functionality tied to the
> app/pyramid - using the commandline / shell for pyramid , i couldn't
> figure out how to run everything with a request object ( as many
> functions are tied to that )
> so i've ended up creating a few views, lock them down, and then turn > them off after I run them.
> nothing has caused a timeout, yet, but i'd like a better option.
> can someone point me in the right direction ?
On Jan 25, 1:46 am, Andreas Jung <li...@zopyx.com> wrote:
> I think using "alembic" seems to be the way to go for
> upgrading/downgrading database schemas.
It is the best for database schema migrations.
But our maintenance largely has to do with internal functions changing
how/where things are stored. A few items didn't have the correct
permalink structure , and things like that. The database isn't
changed, just the data in them ( because we improved something, or
found an edge-case to protect against and fix ).
