Hi Folks,
I'm developing an application using pylons, which involves a bit of
database schema modifying from time to time. Can anyone tell me how
to action changes on the database (managed by sqlalchemy)?
Some things that I've already figured out:
- setting up the initial database is done
On Wed, Apr 22, 2009 at 12:36:09AM -0700, Richard Jones wrote:
I'm developing an application using pylons, which involves a bit of
database schema modifying from time to time. Can anyone tell me how
to action changes on the database (managed by sqlalchemy)?
I think SQLAlchemy Migrate is the
After I updated to pylons 0.9.7 I noticed that my error pages (from
error.py) no longer work.
if I do say abort(404) the browser displays:
301 Moved Permanently
The resource has been moved to http://127.0.0.1:5010/error/document/;
you should be redirected automatically.
The document() handler
On Wed, Apr 22, 2009 at 12:36:09AM -0700, Richard Jones wrote:
Is there a way to access the database directly, so that I can manually
re-jig the database. Or do I have to provide an update script each
time i change the schema? (and if so, how?)
I have a very low-tech solution. I never use
Previously Ross Vandegrift wrote:
On Wed, Apr 22, 2009 at 12:36:09AM -0700, Richard Jones wrote:
Is there a way to access the database directly, so that I can manually
re-jig the database. Or do I have to provide an update script each
time i change the schema? (and if so, how?)
I
On Apr 22, 2009, at 4:45 AM, Max Ischenko wrote:
The document() handler in error.py never called.
middleware setup:
app = StatusCodeRedirect(app, [401, 403, 404, 500])
routing setup:
m.connect('/error/{action}', controller='error')
m.connect('/error/{action}/{id}',
Just to follow up, my problem with Beaker disk-based sessions
On Sat, Mar 14, 2009 at 1:24 PM, Michael Bayer mike...@zzzcomputing.com wrote:
I'd consider memcached sessions since they don't rely on file locks.
On Mar 13, 2009, at 3:31 PM, Mike Orr sluggos...@gmail.com wrote:
--
After upgrading to 0.9.7 I cannot make my routes config work right,
most of the issues were fixed by changing order of rules but there are
also issues that I really do not understand what the problem is
I have two rules
map.connect('company_site_local', 'cs:(id)-:(company_name)/v:
On Apr 22, 2009, at 10:48 AM, Mike Orr wrote:
Just to follow up, my session problems disappeared. I'm not sure
whether it was reinstalling Beaker, or having forgotten to restart the
site after moving it to a new virtualenv. But in any case, it's
running now on Beaker 1.2.3.
I'd highly
On Apr 22, 2009, at 12:41 PM, mickolka wrote:
I have two rules
map.connect('company_site_local', 'cs:(id)-:(company_name)/v:
(vacancy_id)-:(vacancy_title).html', controller='member',
action='vacancy_view', requirements=dict(id='\d+', vacancy_id='\d+'))
map.connect('company_site_local',
here's what i do:
- I always and only use table reflection
- I have a table called 'appschema' that is roughly in pg:
create table app_schema (
id serial,
component varchar(32),
schema_version int,
timestamp_install timestamp
);
create unique index app_schema_uidx on app_schema(
I use SQLAlchemy Migrate. It's an overhead, but has saved me several
times from having to write a lot of SQL to move my data from one
schema to another.
I have an article on SQLAlchemy Migrate here:
http://truefalsemaybe.com/2008/09/sqlalchemy-migrations/
Let me know what you think.
Cheers,
Ben, thanks a lot for reply,
I suspected that it is something about uniqueness of the name of the
route,
but I think that it was a good feature we heavily used in our project.
Why not treat name of the route as alias and do the same as for
unnamed routes - find the most suitable one. It was so
On Wed, Apr 22, 2009 at 10:00 PM, Mykola mpaliye...@gmail.com wrote:
Ben, thanks a lot for reply,
I suspected that it is something about uniqueness of the name of the
route,
but I think that it was a good feature we heavily used in our project.
Why not treat name of the route as alias and
On Wed, Apr 22, 2009 at 19:24, Ben Bangert b...@groovie.org wrote:
It sounds like the StatusCodeRedirect isn't being used. Can you expand to
show what else is in your middleware section. There's a toggle on full_stack
to decide if it should put in the StatusCodeRedirect, do you have
On Apr 22, 2009, at 10:28 PM, Max Ischenko wrote:
But I found the problem:
app = httpexceptions.make_middleware(app, global_conf)
I'm not sure why you need that middleware, its not needed in Pylons
0.9.7, and I didn't think it's been required since 0.9.5 or so?
The Pylons
The Pylons WSGIController handles the exceptions thrown from abort and such,
so that the httpexception middleware is obsolete. What version of Pylons was
used originally for the project?
I do not remember the version but it was something really old. ;)
Anyway, I removed that httpexceptions
17 matches
Mail list logo
